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: unrecognized failures #55308
Comments
Found new dashboard test flakes for:
2022-08-02 18:52 android-arm64-corellium go@4400238e runtime (log)
2022-08-22 14:48 android-arm64-corellium go@6bdca820 runtime (log)
2022-08-25 19:17 android-arm64-corellium go@f64f12f0 runtime (log)
2022-09-06 17:03 android-arm64-corellium go@dc629ec9 runtime (log)
|
Mostly #51001. (Perhaps that issue accounts for all of them?) |
Found new dashboard test flakes for:
2022-09-27 15:57 windows-386-2012 go@e978ef36 runtime (log)
2022-09-27 18:26 android-arm64-corellium go@17078f58 runtime (log)
|
I've updated those with |
The patterns looks good to me. Thanks. |
Found new dashboard test flakes for:
2022-09-28 16:36 linux-ppc64le-power9osu go@9d2c73a9 runtime (log)
2022-09-30 05:48 android-arm64-corellium go@d7dbe011 runtime (log)
2022-10-04 16:03 android-arm64-corellium go@fa463cc9 runtime (log)
|
I don't see where this log is coming from. I don't see it on the build dashboard on that date and I don't see the commit mentioned in the git log for the latest master. |
It's on |
Found new dashboard test flakes for:
2022-12-01 20:48 freebsd-amd64-race go@8ed74ee3 runtime (log)
|
Found new dashboard test flakes for:
2022-11-21 16:27 openbsd-386-71 go@f0331c52 runtime (log)
2023-01-03 20:31 openbsd-386-71 go@9955a7e9 runtime (log)
|
Found new dashboard test flakes for:
2023-01-17 16:11 openbsd-386-71 go@8409251e runtime (log)
2023-01-17 22:30 openbsd-386-71 go@627765a8 runtime (log)
|
Found new dashboard test flakes for:
2023-03-20 20:33 linux-amd64-racecompile crypto@018c28f8 go@f9cf2c4d runtime [build] (log)
|
Another similar looking failure was routed to one of our gopls test flake bugs: |
I left a comment at #57367 (comment). (That particular was a compiler regression that was subsequently reverted.) |
Found new dashboard test flakes for:
2023-04-17 18:44 freebsd-arm-paulzhol go@2068d565 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-04 17:35 android-amd64-emu go@13201d57 runtime (log)
|
Found new dashboard test flakes for:
2023-05-05 19:20 linux-amd64-race go@f90bb8a3 runtime (log)
|
Found new dashboard test flakes for:
2023-05-10 15:11 android-amd64-emu go@93d9035c runtime (log)
|
Found new dashboard test flakes for:
2023-04-18 15:42 freebsd-amd64-race go@56c44227 runtime (log)
|
#60050 again. |
Found new dashboard test flakes for:
2023-05-18 09:15 linux-ppc64-sid-power10 go@27906bb7 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-18 22:02 android-amd64-emu go@edbef1a8 runtime (log)
|
|
Found new dashboard test flakes for:
2023-05-19 20:19 linux-ppc64le-power9osu sys@c8ea6b0c go@45b74d20 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-23 19:15 linux-ppc64-sid-buildlet go@8b51eb51 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-22 18:55 linux-ppc64-sid-buildlet vuln@4d485808 go@e0db8ab6 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-24 03:14 linux-ppc64-sid-buildlet go@626d478d runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-24 13:48 linux-ppc64le-power9osu go@c7f0a8c4 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-24 18:48 linux-ppc64le-power9osu go@5de20f0f runtime [build] (log)
2023-05-24 18:48 linux-ppc64le-power9osu go@5de20f0f runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-24 21:35 linux-ppc64-sid-power10 go@295c237b runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-24 21:17 linux-ppc64le-buildlet go@85e84a49 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-22 18:55 linux-ppc64le-power10osu vuln@4d485808 go@d4bd855c runtime [build] (log)
2023-05-25 01:01 linux-ppc64le-power10osu go@6f7824f7 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-04-27 22:15 linux-ppc64le-buildlet perf@d343f639 go@f0e356a0 runtime [build] (log)
2023-04-27 22:15 linux-ppc64le-buildlet perf@d343f639 go@cfe8b43b runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-26 15:24 linux-ppc64le-power9osu go@a4cd3650 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-22 18:55 linux-ppc64le-power9osu vuln@4d485808 go@3824d3d7 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-25 18:03 linux-ppc64le-power10osu net@f7250ea1 go@7ad92e95 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-23 20:52 linux-ppc64le-power10osu mod@fc83a8fa go@bfa25c3f runtime [build] (log)
|
These are the same failures as in #60368. They started when the compiler
was built with PGO.
…On Tue, May 30, 2023 at 11:48 AM GopherBot ***@***.***> wrote:
Found new dashboard test flakes for:
#!watchflakes
default <- pkg == "runtime" && test == ""
2023-05-23 20:52 linux-ppc64le-power10osu ***@***.*** ***@***.***
runtime [build] (log
<https://build.golang.org/log/0a6108117b0f7247ebaa47c8029d2d2ce1aeca9e>)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x54 pc=0x6906b4]
goroutine 851 [running]:
cmd/compile/internal/types.(*Type).Size(...)
cmd/compile/internal/types/type.go:973
cmd/compile/internal/ssagen.TypeOK(0x0)
cmd/compile/internal/ssagen/ssa.go:5573 +0x34
cmd/compile/internal/ssagen.(*state).stmt(0xc00627a800, {0xacf408, 0xc001ad37c0?})
cmd/compile/internal/ssagen/ssa.go:1660 +0x5f3c
cmd/compile/internal/ssagen.(*state).stmtList(...)
cmd/compile/internal/ssagen/ssa.go:1417
cmd/compile/internal/ssagen.buildssa(0xc0018cf600, 0x3)
cmd/compile/internal/ssagen/ssa.go:548 +0x235c
cmd/compile/internal/ssagen.Compile(0xc0018cf600, 0x0?)
cmd/compile/internal/ssagen/pgen.go:187 +0x48
cmd/compile/internal/gc.compileFunctions.func5.1(0x0?)
cmd/compile/internal/gc/compile.go:184 +0x4c
cmd/compile/internal/gc.compileFunctions.func3.1()
cmd/compile/internal/gc/compile.go:166 +0x48
created by cmd/compile/internal/gc.compileFunctions.func3 in goroutine 163
cmd/compile/internal/gc/compile.go:165 +0x20c
— watchflakes <https://go.dev/wiki/Watchflakes>
—
Reply to this email directly, view it on GitHub
<#55308 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACH7BDCQBKFLUMWHLCJIM53XIYQHFANCNFSM6AAAAAAQSLLXU4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Found new dashboard test flakes for:
2023-04-27 22:15 aix-ppc64 perf@d343f639 go@993707a9 runtime [build] (log)
|
Found new dashboard test flakes for:
2023-05-31 19:56 linux-ppc64le-power10osu go@9552a112 runtime [build] (log)
|
In triage, I don't see anything new to break out here? Leaving this comment as a marker for next time. |
The problem I mentioned earlier was fixed by https://go-review.googlesource.com/c/go/+/499679 which for some reason became apparent when PGO was used to build the compiler. This problem affected all ppc64/ppc64le ports since it was bug in the ppc64 version of the gc write barrier flush and resulted in several different stack traces from the compile step. We've not seen that particular problem since. |
Found new dashboard test flakes for:
2023-08-16 16:51 linux-riscv64-unmatched go@e82cb142 runtime [build] (log)
|
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: