-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: lock ordering problems #58277
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Found new dashboard test flakes for:
2023-01-17 19:55 linux-amd64-staticlockranking go@839c8425 runtime/trace.TestTraceFutileWakeup (log)
|
Found new dashboard test flakes for:
2023-05-19 14:59 linux-amd64-staticlockranking go@251daf46 runtime.TestPinnerSimple (log)
2023-05-19 15:54 linux-amd64-staticlockranking go@f283cba3 runtime.TestPinnerSimple (log)
|
cc @mknyszek these look related to pinning |
They're fixed at HEAD. :) Forgot to reference the issue because the change landed before this issue was updated. |
Found new dashboard test flakes for:
2023-05-11 14:15 linux-amd64-staticlockranking go@e738f130 os/signal.TestSignalTrace (log)
|
I don't understand this last failure because |
Commit (I filed #59483 to request clearer output from |
Found new dashboard test flakes for:
2023-05-23 11:37 linux-amd64-staticlockranking go@c99d966c runtime.TestPinnerSimple (log)
|
Okay, this last one is my bad. Should've seen that coming. |
Change https://go.dev/cl/497475 mentions this issue: |
CL 493275 started using gcBits for pinner bits. This means gcBits can be allocated while holding the mspanSpecial lock. This is safe because these were just parallel in the partial order, but now they need an explicit edge between them. For #58277. Change-Id: I37917730e12d59cf0580f198d732198413a56424 Reviewed-on: https://go-review.googlesource.com/c/go/+/497475 Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com>
I don't think we have any new ones. Moving this to Backlog. |
Found new dashboard test flakes for:
2023-10-25 19:47 linux-amd64-staticlockranking go@a57c5736 runtime/trace.TestTraceFutileWakeup (log)
|
Found new dashboard test flakes for:
2023-12-01 19:20 linux-amd64-staticlockranking go@5a2161ce runtime (log)
|
Found new dashboard test flakes for:
2023-12-06 17:59 linux-amd64-staticlockranking go@3f2bf706 runtime (log)
|
Found new dashboard test flakes for:
2023-12-13 00:22 linux-amd64-staticlockranking go@400e24a8 runtime (log)
|
gscan -> profInsert split to #64706. |
Found new dashboard test flakes for:
2024-01-23 00:14 linux-amd64-staticlockranking go@4605ce2d os/signal (log)
|
Found new dashboard test flakes for:
2024-01-25 09:18 gotip-linux-amd64-staticlockranking go@cad66291 os/signal.TestNotifyContextNotifications (log)
2024-01-25 09:18 gotip-linux-amd64-staticlockranking go@cad66291 os/signal.TestSignalTrace (log)
|
Found new dashboard test flakes for:
2024-02-21 21:27 linux-amd64-staticlockranking go@cdf3249d net/http/pprof (log)
|
Found new dashboard test flakes for:
2024-02-28 16:43 linux-amd64-staticlockranking go@3be36e9b net/http/pprof (log)
|
Found new dashboard test flakes for:
2024-03-08 22:34 linux-amd64-staticlockranking go@24fa7544 net/http/pprof (log)
|
Found new dashboard test flakes for:
2024-03-25 19:21 linux-amd64-staticlockranking go@2c677361 net/http/pprof (log)
|
Found new dashboard test flakes for:
2024-04-16 14:45 linux-amd64-staticlockranking go@f17b28de net/http/pprof (log)
|
Found new dashboard test flakes for:
2024-04-15 20:09 gotip-linux-amd64-staticlockranking go@7418d419 net/http/pprof.TestDeltaProfile [ABORT] (log)
|
Found new dashboard test flakes for:
2024-05-07 15:28 go1.22-linux-amd64-staticlockranking release-branch.go1.22@fa0292d2 net/http/pprof (log)
2024-05-07 15:28 go1.22-linux-amd64-staticlockranking release-branch.go1.22@fa0292d2 net/http/pprof.TestDeltaProfile [ABORT] (log)
|
(Pulled out from #55167, because these issues tend to be easier to diagnose; CC @golang/runtime)
The text was updated successfully, but these errors were encountered: