> I'm seeing something that looks to me like a resource exhaustion of some > sort. When running the standard test (i.e. go test std), some tests are > broken (see below); but test of each "broken" package/cmd/etc, passes > correctly.
I would agree with you, that is the impression I get as well, but the little monitoring I've applied as well as the fact that I have three very different hosts right here all exhibiting analogous but distinct failures makes me think of time/performance related crashes. On the other hand, cinap may be onto something: if we have a floating point failure followed by a timer signal, all hell is perfectly entitled to break loose. But floating point isn't always involved. We'll get to the bottom of this, eventually, we just need as many informative data points as possible. ++L
