-
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
cmd/trace: unrecognized failures #56785
Comments
Found new dashboard test flakes for:
2022-11-07 17:58 dragonfly-amd64-622 website@0bdc4717 go@a6642e67 cmd/trace [build] (log)
2022-11-07 17:58 dragonfly-amd64-622 website@0bdc4717 go@41be62e1 cmd/trace [build] (log)
2022-11-07 21:25 dragonfly-amd64-622 tools@003fde14 go@6939659a cmd/trace [build] (log)
|
Duplicate of #56787 |
Found new dashboard test flakes for:
2023-01-24 19:47 freebsd-arm-paulzhol go@ffbd194f cmd/trace (log)
|
Found new dashboard test flakes for:
2023-08-01 14:26 linux-riscv64-unmatched go@d4b46b09 cmd/trace [build] (log)
|
This looks like memory corruption on RISC-V. Is there an open issue for that? |
The latest failure is definitely not the same as the previous failures here. I'll close this and open a new issue. |
For the moment, to stop |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: