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: TestGdbBacktrace failures #58698
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Comments
Found new dashboard test flakes for:
2023-02-13 19:42 linux-386-longtest go@0b922bfa runtime.TestGdbBacktrace (log)
|
In triage, best guess is that this is just a "GDB tests are sometimes flaky" but we'll wait on more failures. Than and Cherry note that the GDB version isn't very old. |
Found new dashboard test flakes for:
2023-03-16 19:44 linux-arm64 go@19281498 runtime.TestGdbBacktrace (log)
|
Found new dashboard test flakes for:
2023-03-16 19:51 linux-arm64-boringcrypto go@e91876f4 runtime.TestGdbBacktrace (log)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: