I can replicate this on another newer RHEL machine. In both cases the machines are quiet (they are the head nodes of HPC infrastructure and don't see a great deal of work due to the HPC use policy.
I have tried building previous versions and see similar though different failures going back to 1.7 (where I stopped). In those cases there is also a timeout, and waiting for things seems also to be the issue. Should I file an issue? Suggested title? Should I post stack traces for previous versions? thanks On Thu, 2017-09-28 at 10:11 -0700, Ian Lance Taylor wrote: > On Wed, Sep 27, 2017 at 10:20 PM, Dan Kortschak > <dan.kortsc...@adelaide.edu.au> wrote: > > > > > > I am seeing all.bash fail when testing cmd/go with a likely cause > > being > > internal/poll.runtime_pollWait. > > > > I'm trying to build go1.9 (with a change to the heap size), but > > all.bash fails as shown below. Is this a known problem? and if it > > is, > > is there a workaround. > This is not a known problem. > > It does not look like the problem has anything to do with > runtime_pollWait. The test being run is > TestGoTestCpuprofileDashOControlsBinaryLocation in cmd/go/go_test.go. > That test runs the go tool itself, specifically running `go test > -cpuprofile errors.prof -o myerrors.test errors`. The stack trace > you > included (thanks for doing that) shows that cmd/go/go_test.go is > waiting for that execution to complete. > > There is an overall timeout of 3 minutes. If your machine is slow > for > some reason it is possible that the cmd/go tests are simply timing > out. Or, it is possible that the execution invoked by > TestGoTestCpuprofileDashOControlsBinaryLocation is hanging for some > reason, though I don't know why that would happen. > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
