Closed bcmills closed 3 days ago
Found new dashboard test flakes for:
#!watchflakes
post <- goarch == "wasm" && pkg == "golang.org/x/tools/go/ssa" && `fatal error: found bad pointer in Go heap`
Found new dashboard test flakes for:
#!watchflakes
post <- goarch == "wasm" && pkg == "golang.org/x/tools/go/ssa" && `fatal error: found bad pointer in Go heap`
Found new dashboard test flakes for:
#!watchflakes
post <- goarch == "wasm" && pkg == "golang.org/x/tools/go/ssa" && `fatal error: found bad pointer in Go heap`
Found new dashboard test flakes for:
#!watchflakes
post <- goarch == "wasm" && pkg == "golang.org/x/tools/go/ssa" && `fatal error: found bad pointer in Go heap`
Change https://go.dev/cl/612398 mentions this issue: go/ssa: disable TestTypeparamTest/chan.go on wasm
Relevant line is:
go/types.(*typeWriter).typ(0x182d790, {0x1375f0, 0xa0b6b58})
/home/swarming/.swarming/w/ir/x/w/goroot/src/go/types/typestring.go:120 +0x6 fp=0x182d678 sp=0x182d4b8 pc=0x22750006
Relevant code:
w.seen[typ] = true // <- complaint is here
defer delete(w.seen, typ)
My hunch is that this is an interaction with the next line defer delete(w.seen, typ)
on wasm, but I am not sure. I'm going to disable the flaky test for now, but wasm folks might want to take a look. CC @golang/wasm
Go version
N/A
What operating system and processor architecture are you using (
go env
)?What did you do?
Check
x/tools
LUCI builder status: https://ci.chromium.org/p/golang/g/x-tools-gotip/consoleWhat did you expect to see?
All tests passing.
What did you see instead?
A pattern of failures on the
js/wasm
builders involving apointer … to unused region of span
when running a particularx/tools
test that doesn't fail anywhere else.Examples:
(attn @golang/wasm)