Skip to content
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

runtime: rare TestSpuriousWakeupsNeverHangSemasleep failures #38921

FiloSottile opened this issue May 7, 2020 · 3 comments

runtime: rare TestSpuriousWakeupsNeverHangSemasleep failures #38921

FiloSottile opened this issue May 7, 2020 · 3 comments


Copy link

@FiloSottile FiloSottile commented May 7, 2020

Got one on the SlowBot for CL 227037.

--- FAIL: TestSpuriousWakeupsNeverHangSemasleep (2.02s)
    semasleep_test.go:51: Program failed to return on time and has to be killed, issue #27520 still exists
FAIL	runtime	80.585s

I am messing with the runtime in that CL but I don't see how it would be related to this, and I found two more in ~recent build dashboard logs.

greplogs -E TestSpuriousWakeupsNeverHangSemasleep -dashboard -l -md


Looks like it also failed during a release #37199 (comment) and in Sept 2019 for someone who then did not follow-up #27520 (comment).

Copy link

@toothrot toothrot commented May 11, 2020

@toothrot toothrot added this to the Backlog milestone May 11, 2020
Copy link

@randall77 randall77 commented May 11, 2020


Those other two errors you found grepping the logs look different. They are not timeouts.

I think we might need to just increase the timeout. If there is too much work going on on the machine, timers, or responses to them, might be delayed.

Copy link

@bcmills bcmills commented Nov 9, 2020

2020-11-05T22:14:40-8e5778e/linux-riscv64-jsingsignal: I/O possible
2020-10-12T15:38:05-2e7706d/darwin-amd64-raceProgram failed to return on time and has to be killed
2020-08-18T08:47:48-4149493/solaris-amd64-oraclerelsignal: pollable Event
2020-06-17T15:09:07-f84bbd5/openbsd-arm-jsingProgram failed to return on time and has to be killed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants