build: compiler OOM on android-arm64-corellium builder

[gopherbot]

#!watchflakes
post <- builder == "android-arm64-corellium" && `compile: signal: killed`

Issue created automatically to collect these failures.

Example (log):

FAIL
go tool dist: Failed: exit status 1

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- section == "Testing packages." && test == ""

2022-11-28 15:02 android-arm64-corellium go@cc7530da (log)

FAIL
go tool dist: Failed: exit status 1

2022-12-02 16:30 plan9-386-0intro go@d71b1c3d io.test [build] (log)

link 16879: suicide: sys: trap: fault write addr=0x766e652f pc=0x000060ad

2022-12-02 21:15 plan9-386-0intro go@45f5ef4e (log)

fatal error: unexpected signal during runtime execution
[signal sys: trap: fault write code=0x0 addr=0x0 pc=0x6d947]

runtime stack:
runtime.throw({0x9d68d8, 0x2a})
	/tmp/workdir-gnot/go/src/runtime/panic.go:1047 +0x4d fp=0xdfffee38 sp=0xdfffee24 pc=0x3bc4d
runtime.sigpanic()
	/tmp/workdir-gnot/go/src/runtime/os_plan9.go:80 +0x4a2 fp=0xdfffee78 sp=0xdfffee38 pc=0x38162
runtime.rfork()
	/tmp/workdir-gnot/go/src/runtime/sys_plan9_386.s:139 +0x7 fp=0xdfffee7c sp=0xdfffee78 pc=0x6d947
...
goroutine 1 [running]:
runtime.systemstack_switch()
	/tmp/workdir-gnot/go/src/runtime/asm_386.s:337 fp=0x9846fbc sp=0x9846fb8 pc=0x6b9c0
runtime.main()
	/tmp/workdir-gnot/go/src/runtime/proc.go:170 +0x6e fp=0x9846ff0 sp=0x9846fbc pc=0x3e22e
runtime.goexit()
	/tmp/workdir-gnot/go/src/runtime/asm_386.s:1326 +0x1 fp=0x9846ff4 sp=0x9846ff0 pc=0x6cd51
go: error obtaining buildID for go tool compile: exit status: 'compile 11139: 2'

go tool dist: FAILED: go list -f={{if .Stale}}	STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std cmd: exit status: 'go 11134: 1'

— watchflakes

[bcmills]

Duplicate of #54819

[bcmills]

I think this indicates a watchflakes bug of some sort. It should not have created a new issue for these failures.

• The android-arm64-corellium failure should have gone to existing issue x/build: corellium builders failing with signal: killed #54819.
• The plan9-386-0intro failures should have gone to existing issue all: unrecognized failures on plan9-386-0intro #57115.