cmd/compile/internal/ssa: failure of TestFmaHash #61192
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
|
That's strange. Can you add a What directory are you building in? Maybe that test is not picking up the right go instance. The Maybe unset your |
|
I don't have a I'm running another build with the change you requested. |
|
This is the log with the added printout. PS: The failure looks the same using gcc 10.3.0 instead of 4.8.5 from CentOS Edit: Tried to use the summary thing for collapsible log output, but that triggers markdown parsing inside. Now back to simple backticks. |
|
This looks like it may be the problem.
Is your
Ok, I misunderstood your |
|
Oh, out of disk space … that's embarrassing that I didn't check that last and profound error. Will try next week with antother location. But … there's over 80G free. It's a shared filesystem, so that may have changed. But still, does the test need dozens of GiB? |
I'm not sure. |
|
Even with The usage was 'only' around 1.5G max in the work directory and 1.2G in |
bcmills
added
the
compiler/runtime
bcmills
changed the title
bcmills
added
the
NeedsInvestigation
|
I'm having a go with go 1.21.1. After patching out fmahash test using I get a similar failure in another test: These spurious out-of-disk-space errors are getting worse? Is this a feature of the go compiler/linker? This is a local disk with 86G free space. This has to be enough to compile and test golang! A search for 'no space left on device' in the issues here indicates that my setup is not the only one suffering from this. I'm going to try and patch out the loopvar test, too. |
|
OK, I managed to build go-1.21.0 now with three sets of changes.
The third one is new. I get a complaint that the expected mtime does not match after the rewrite. The difference Anyhow, that is my current hack for 2 and 3: It is telling that those skipped tests already had safeguards about them being expensive. Apparently |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version)?I am trying to build go 1.20.5 using a pre-built go 1.17.3 on a CentOS 7.9 system with Haswell CPUs.
Does this issue reproduce with the latest release?
Well … I am trying to bootstrap to the latest release …
What operating system and processor architecture are you using (
go env)?go envOutputWhat did you do?
Basically
What did you expect to see?
A completed build with all tests passing.
What did you see instead?
Building Go cmd/dist using /sw/env/system-gcc/go/1.17.13. (go1.17.13 linux/amd64) Building Go toolchain1 using /sw/env/system-gcc/go/1.17.13. Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1. Building Go toolchain2 using go_bootstrap and Go toolchain1. Building Go toolchain3 using go_bootstrap and Go toolchain2. Building packages and commands for linux/amd64. ##### Test execution environment. # GOARCH: amd64 # CPU: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz # GOOS: linux # OS Version: Linux 4.14.295-1.0.41.el7.rrz.x86_64 #1 SMP Wed Dec 14 00:03:35 CET 2022 x86_64 ##### Testing packages. ok archive/tar 0.246s ok archive/zip 0.157s ok bufio 0.082s ok bytes 0.299s […] ok cmd/compile/internal/ir 0.035s ok cmd/compile/internal/logopt 0.318s ok cmd/compile/internal/noder 0.067s ok cmd/compile/internal/reflectdata 0.048s [no tests to run] --- FAIL: TestFmaHash (6.39s) fmahash_test.go:45: /scratch/sw/work/system-gcc/go/1.20.5/go/bin/go build -o /work/sw/tmpdir/x2243797535/fma.exe testdata/fma.go fmahash_test.go:46: [GOCOMPILEDEBUG=fmahash=1/0 GOOS=linux GOARCH=arm64 HOME=/work/sw/tmpdir/x2243797535] fmahash_test.go:49: exit status 1 FAIL FAIL cmd/compile/internal/ssa 36.076s ok cmd/compile/internal/syntax 0.089s ok cmd/compile/internal/test 17.227s ok cmd/compile/internal/typecheck 1.355s ok cmd/compile/internal/types 0.049s […] ok cmd/pprof 3.836s ok cmd/trace 1.042s ok cmd/vet 14.622s FAIL go tool dist: Failed: exit status 1The text was updated successfully, but these errors were encountered: