-
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
runtime: TestGdbAutotmpTypes failures #69527
Comments
Found new dashboard test flakes for:
2024-09-18 19:48 gotip-linux-riscv64 go@c71b5ff7 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-18 15:49 gotip-linux-riscv64 go@889178d5 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-18 13:16 gotip-linux-riscv64 go@d682a9df runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-17 15:51 gotip-linux-riscv64 go@41ca2637 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-16 19:10 gotip-linux-riscv64 go@72739bbf runtime.TestGdbAutotmpTypes (log)
|
CC @golang/riscv64 |
This is failing quite regularly. The linux-riscv64 builder is almost 100% red due to this failure. It also seems new, so perhaps a regression. |
Related to #67089 |
Found new dashboard test flakes for:
2024-09-18 19:41 go1.23-linux-riscv64 release-branch.go1.23@c8c6f9ab runtime.TestGdbAutotmpTypes (log)
2024-09-23 16:29 gotip-linux-riscv64 go@ab5c22e7 runtime.TestGdbAutotmpTypes (log)
2024-09-23 18:00 gotip-linux-riscv64 go@dfd0f0d8 runtime.TestGdbAutotmpTypes (log)
2024-09-23 18:01 gotip-linux-riscv64 go@530fbb28 runtime.TestGdbAutotmpTypes (log)
2024-09-24 17:10 gotip-linux-riscv64 go@43cf7318 runtime.TestGdbAutotmpTypes (log)
2024-09-24 18:31 gotip-linux-riscv64 go@03fecda0 runtime.TestGdbAutotmpTypes (log)
2024-09-25 15:13 gotip-linux-riscv64 go@6cb10745 runtime.TestGdbAutotmpTypes (log)
2024-09-25 17:30 gotip-linux-riscv64 go@c64ca8c6 runtime.TestGdbAutotmpTypes (log)
2024-09-25 17:31 gotip-linux-riscv64 go@49e542aa runtime.TestGdbAutotmpTypes (log)
2024-09-25 20:04 gotip-linux-riscv64 go@8ed18d2c runtime.TestGdbAutotmpTypes (log)
2024-09-26 14:01 gotip-linux-riscv64 go@906338f8 runtime.TestGdbAutotmpTypes (log)
2024-09-26 17:06 gotip-linux-riscv64 go@ca1123f9 runtime.TestGdbAutotmpTypes (log)
2024-09-26 20:13 gotip-linux-riscv64 go@b7e4d206 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-26 19:42 gotip-linux-riscv64 go@ca3b1b13 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-26 16:51 gotip-linux-riscv64 go@ba421207 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-26 14:28 gotip-linux-riscv64 go@9b1f8f32 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-26 13:18 gotip-linux-riscv64 go@6d856a80 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-24 19:51 gotip-linux-riscv64 go@68bcef7e runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-09-27 18:23 go1.23-linux-riscv64 release-branch.go1.23@3b2e846e runtime.TestGdbAutotmpTypes (log)
|
This comment was marked as outdated.
This comment was marked as outdated.
@gopherbot Please backport to 1.23 and 1.22. This is a test-only fix due to a change on the builders (new version of GDB). Hence release branches are also flaking. |
Backport issue(s) opened: #69745 (for 1.22), #69746 (for 1.23). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Found new dashboard test flakes for:
2024-10-01 17:24 go1.22-linux-riscv64 release-branch.go1.22@aeccd613 runtime.TestGdbAutotmpTypes (log)
|
Found new dashboard test flakes for:
2024-10-22 18:15 gotip-linux-riscv64 go@ad7f736d runtime.TestGdbAutotmpTypes [ABORT] (log)
|
Found new dashboard test flakes for:
2024-11-11 00:08 gotip-linux-riscv64 go@4b89120b runtime.TestGdbAutotmpTypes [ABORT] (log)
|
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: