-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: darwin mach error semaphore_wait: 49 #17161
Comments
Error 49 is |
Possibly related to #16646, which also shows a semaphore operation with no timeout failing, albeit on Windows. |
Also happened on the trybot for https://go-review.googlesource.com/c/29270/ |
And a non-trybot: https://build.golang.org/log/1e9c01fc095bd7d8e622fd38f47d569f585ee8d7 |
Same error in this trybot run: |
On the dashboard runs, this started in late July 2016. These are the dashboard failures (searching back to March):
The first commit that failed (ea2376f) had nothing to do with OS X, nor did anything immediately before it. The first obvious suspect before that commit is ff227b8 (CL 25104) but I can't see that doing anything. The next obvious suspect is 50048a4 (CL 25047) but again I can't see a problem. It does seem like there's just an OS X kernel bug here, but I don't know why it only started showing up recently. My comment in the meeting earlier today, that this was a recent Go change that made the code more strict, appears to be wrong. I'm not sure what I was thinking of, but this code is unchanged since the translation to Go in November 2014. @bradfitz, did something about the OS X builders themselves change in late July? |
That might've been when we switched to VMWare-based builders. Can confirm after dinner. |
CL https://golang.org/cl/31823 mentions this issue. |
No, the builders didn't switch to VMWare until early September (Sep 6th/7th), with some testing starting Aug 30th. |
A trybot run failed, unable to build a package on Darwin:
https://go-review.googlesource.com/c/29390/
https://storage.googleapis.com/go-build-log/31a66204/darwin-amd64-10_11_93806cd8.log
The text was updated successfully, but these errors were encountered: