Open bcmills opened 1 year ago
Sorry, but there were parse errors in the watch flakes script. The script I found was:
#!watchflakes
builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
And the problems were:
script:2.9: unexpected ~
See https://go.dev/wiki/Watchflakes for details.
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
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:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
I don't understand this last failure because traceStrings < MALLOC < fin
explicitly in the lock rank order...
Commit e738f130
is on release-branch.go1.19
(https://go.googlesource.com/go/+/e738f130).
(I filed #59483 to request clearer output from watchflakes
for the release branches.)
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Okay, this last one is my bad. Should've seen that coming.
Change https://go.dev/cl/497475 mentions this issue: runtime: add partial lock order between mspanSpecial and gcBitsArenas
I don't think we have any new ones. Moving this to Backlog.
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
gscan -> profInsert split to #64706.
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
@mknyszek I think adding traceStackTab
above WB
would be OK?
Edit: oh, nevermind. I see #56554 now.
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
Found new dashboard test flakes for:
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
(Pulled out from #55167, because these issues tend to be easier to diagnose; CC @golang/runtime)