On Thu, Sep 28, 2017 at 10:12 PM, Dan Kortschak <dan.kortsc...@adelaide.edu.au> wrote: > > I have just tried replicating the issue today and this time, one > machine passes everything, while the other does not. I am beginning to > suspect that file system loads may be a possible cause (the head node > is quiet, but the file system is shared across many nodes in both > cases). > > The newer machine is 3.10.0-514.2.2.el7.x86_64 (also RHEL7). > > I will raise this internally and get back to the issue if they don't > think this is the case. Unfortunately the two machines are under > different management, so it may be difficult to get a clear idea of > what's going on. > > There are a variety of test goroutines in the stack trace (as is the > case with the original) the test you point out is not consistently in > the stack trace for either version. The stack trace for 1.8.3 is pasted > below. > > Running `go test -cpuprofile errors.prof -o myerrors.test errors` > passes without event.
In the stack trace you just posted the failing test is TestTestRaceInstall. What happens if you run simply `go test -test.short cmd/go`? If it passes, how long does it take? 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.
