-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: new timer code breaks TestLockedDeadlock2 on Solaris #35393
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
See previously #35274. |
That is almost certainly #35375. |
The |
Confirmed: after I've updated my tree to that commit, runtime passes reliably.
Yes, every build in the last couple of days has been failing on the solaris-amd64 builder. I'll try your proposed patch momentarily. |
Just finished: both the testsuite as a whole passes, and repeated runs of |
Thanks. I just submitted https://golang.org/cl/205558, so I think we are good here. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
For a couple of days, the solaris-amd64 builder has been failing most of the the time, while
until Oct 31 it has been almost completely reliable.
This started off as a failure in runtime.TestLockedDeadlock2.
What did you expect to see?
The test should continue to pass as before.
What did you see instead?
It started to fail like this
This started at commit 6becb03, while reverting to
commit 81a74b4 lets the test pass reliably.
Meanwhile, the situation of the builder has become even worse with the cmd/go always timing out
after 20 minutes, mostly blocking the builder. It's hard to tell if this is a consequence of the
same issue or something completely different, so I'll hold off reporting it until this issue is resolved.
The text was updated successfully, but these errors were encountered: