I'm not sure how I would check do you have suggestions? Also, is there a way to just run the failing test rather than redoing the whole build? Documentation on the build process seems sparse.
On Friday, 10 July 2020 15:54:02 UTC-4, David Riley wrote: > > On Jul 10, 2020, at 3:02 PM, Alastair Neil <ajnei...@gmail.com > <javascript:>> wrote: > > > > > > It's an old but not an especially slow machine: dual 8 core E5-2670 Xeon > with 64 GB Ram. > > I wil try > > GO_TEST_TIMEOUT_SCALE=4 > > I've successfully built on an older and slower (pre-Nehalem) 8-core Xeon > with a similar RAM load just last week, so it's probably not that. > > Is something amiss with your system's timer setup? The tick tests seem > wrong, but precisely near 100ms boundaries. It almost looks like you have > 10 Hz scheduler ticks and it's not seeing the granularity it should (and > maybe getting scheduled later than expected). > > > - Dave > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/63a1d572-695c-462b-a83b-b37d916c512bo%40googlegroups.com.
