You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can the test be modified to print out more information about the failure?
Maybe stderr has more information. Exit status 2 is not enough.
Who could be sending a kill signal, could that due to timing out?
I'll see if I can reproduce the problem.
I thought there would be more information about the failure than just "exit status 2".
This test appears to be rebuilding the toolchain using the toolchain it just built as its bootstrap compiler. Doesn't that mean it will be changing/updating components of the toolchain as it is using those components for the new build?
go build cmd/compile/internal/ssa: /workdir/tmp/reboot-goroot202913779/pkg/tool/linux_ppc64le/compile: exit status 1
go tool dist: FAILED: /workdir/tmp/reboot-goroot202913779/pkg/tool/linux_ppc64le/go_bootstrap install -gcflags=all= -ldflags=all= -a -i cmd/asm cmd/cgo cmd/compile cmd/link: exit status 1
--- FAIL: TestRepeatBootstrap (100.86s)
reboot_test.go:50: exit status 2
Here it is using /workdir/tmp/reboot-goroot202913779/pkg/tool/linux_ppc64le/compile to compile with but the result is an install of cmd/compile.