https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89406
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yes, some go tests fail pretty much all the time for me, but with quite high volatility, so I usually ignore them if there aren't too many. This time FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments FAIL: go.test/test/nilptr2.go execution, -O2 -g FAIL: go test cmd/go FAIL: go test runtime on x86_64-linux and FAIL: ./index0-out.go execution, -O0 -g -fno-var-tracking-assignments FAIL: go test cmd/go FAIL: TestScript FAIL: go test runtime FAIL: TestAbort on i686-linux.
