-
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
runtime: TestGdbBacktrace failures #58698
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)
|
Found new dashboard test flakes for:
2023-03-30 18:50 linux-amd64 go@8890c3a0 runtime.TestGdbBacktrace (log)
|
Even if the problem is “GDB tests are sometimes flaky”, arguably they ought to skip in case of known failure modes. (At the very least, there ought to be specific upstream issues we can refer to for the failures — if the problem is upstream and we don't report it, then it presumably won't ever get fixed.) |
Found new dashboard test flakes for:
2023-05-04 17:01 linux-arm64 go@8337ca09 runtime.TestGdbBacktrace (log)
|
https://storage.googleapis.com/go-build-log/d8316abe/linux-amd64-longtest_5f06b423.log (a SlowBot on CL 499855) |
@golang/runtime, could someone please at least update the skips for this test? If the problem is “GDB is flaky” we shouldn't be annoying Go developers (and Go users who run |
Change https://go.dev/cl/499975 mentions this issue: |
Found new dashboard test flakes for:
2023-06-05 16:41 linux-ppc64le-power10osu go@587c1c19 runtime.TestGdbBacktrace (log)
|
Change https://go.dev/cl/500959 mentions this issue: |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: