-
Notifications
You must be signed in to change notification settings - Fork 18k
sync: TestCondBroadcast failures #61874
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
Labels
arch-riscv
Issues solely affecting the riscv64 architecture.
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
help wanted
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
Found new dashboard test flakes for:
2023-08-08 17:51 linux-riscv64-unmatched go@0c13bd63 sync.TestCondBroadcast (log)
|
(attn @golang/riscv64) |
I ran 10000 Broadcast test without issue. |
A lot of these low-level hard-to-reproduce bugs turn out to be corruption in signal handlers. Maybe the failure depends on some other (perhaps CPU-bound) test running concurrently, causing the runtime to self-signal for preemption? |
Found new dashboard test flakes for:
2023-08-09 14:36 linux-riscv64-unmatched go@288fd6eb sync.TestCondBroadcast (log)
|
Related: #62185 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-riscv
Issues solely affecting the riscv64 architecture.
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
help wanted
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: