Open bcmills opened 9 months ago
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Similar to #64650, I wonder if this would be fairly straightforward to bisect. If anyone from @golang/s390x has time and easier access to a machine, it'll hopefully be straightforward to identify the root cause, if bisection is feasible.
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestSignalForwardingGo" && `got "signal: aborted \(core dumped\)"`
Go version
c29444ef39a44ad56ddf7b3d2aa8a51df1163e04
What operating system and processor architecture are you using (
go env
)?What did you do?
https://build.golang.org/log/78e761f843d3796f9ba2417bc7aa9195b53fd982
What did you expect to see?
All tests passing.
What did you see instead?
(attn @golang/s390x)