On Jul 10, 2020, at 3:02 PM, Alastair Neil <ajneil.t...@gmail.com> 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/46244F14-A133-4E5C-B54E-49C703F73921%40gmail.com.
