-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: static lock ranks fail on darwin/amd64 #66386
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
Broken versions include Maybe it's a missing edge in mklockrank.go? |
Only GOOS=darwin and GOOS=ios interact with the execlock during CC @mknyszek and @prattmic — you're both close to the builders (maybe we need one for GOOS=darwin + GOEXPERIMENT=staticlockranking?) and to the scheduler / lock ranking. I haven't dug in to how the exec lock interacts with the scheduler, and if the fix here is as simple as moving Lines 362 to 373 in 2e8d84f
|
But But (again), I also see that @mknyszek , do these represent real (rare) deadlock risks? From a recent version of tip with un-committed local changes implementing the above (so don't trust the line numbers):
|
Duplicate of #66386, I think? |
Go version
go version devel go1.23-0a6f05e30f Sun Mar 17 15:57:54 2024 +0000 darwin/amd64
Output of
go env
in your module/workspace:What did you do?
I visited build.golang.org, found the most recent commit that had succeeded on the linux/amd64 staticlockranking builders, and tried to replicate that success on my darwin/amd64 machine.
What did you see happen?
What did you expect to see?
I expected
GOEXPERIMENT=staticlockranking
to work on darwin, in addition to working on linux.The text was updated successfully, but these errors were encountered: