-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
internal/trace: TestTraceGOMAXPROCS/Default failures #68878
Labels
arch-loong64
Issues solely affecting the loongson architecture.
compiler/runtime
Issues related to the Go compiler and/or runtime.
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:
2024-08-14 18:07 gotip-linux-loong64 go@3c170ac0 internal/trace.TestTraceGOMAXPROCS/Default (log)
|
CC @golang/loong64 This looks like some kind of memory corruption, probably not actually related to tracing. |
I also found that the memory of the Loong64 builder is not very reliable, and I am planning to replace these builders. |
Found new dashboard test flakes for:
2024-08-23 10:40 gotip-linux-riscv64 go@6d55a017 internal/trace.TestTraceGOMAXPROCS/Default (log)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
arch-loong64
Issues solely affecting the loongson architecture.
compiler/runtime
Issues related to the Go compiler and/or runtime.
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: