-
Notifications
You must be signed in to change notification settings - Fork 18.1k
runtime: all.bash intermittent hang running test for issue 19182 #23560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Has this happened more than once? How many cores do you have on your system? |
So far I've only seen it the first time running all.bash after updating to 1.10rc1. I can run all.bash in a loop and see if it happens again.
4
|
all.bash ran 120 times in a row without issue. Closing as a freak occurrence. |
If you'd like to make sure, in a more efficient manner, you could also do something like this: $ go get golang.org/x/tools/cmd/stress
$ go build -o issue19182 test/fixedbugs/issue19182.go
$ stress ./issue19182 -timeout 1m and let it run for a while (obviously at least a minute!)... |
@josharian Thanks, I'll try that and report back. |
@josharian 1 million runs and no failures. Thanks for the pointer to "stress", though! |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go1.10rc1
Does this issue reproduce with the latest release?
Yes, assuming go1.10rc1 is considered the latest release
What operating system and processor architecture are you using (
go env
)?What did you do?
I ran all.bash after checking out the go1.10rc1 tag.
What did you expect to see?
all.bash complete successfully
What did you see instead?
all.bash hung on the issue19182 test for ~5 minutes before I killed it. During that time the issue19182 process was taking up ~100% CPU in "top".
Running all.bash a second time ran to completion.
Below is the SIGQUIT dump from killing all.bash:
The text was updated successfully, but these errors were encountered: