<pre class="notranslate">ok      text/template/parse     0.007s
--- FAIL: TestOverflowRuntimeTimer (0.10 seconds)
        sleep_test.go:402: runtime timer stuck: overflow in addtimer
FAIL
FAIL    time    4.651s

Fails on several builds, FreeBSD, OpenBSD, Windows. I believe all these builders are
running inside vm's so this could be related

What is the expected output? What do you see instead?

Is this test failure an actual problem, or just noise by slow builders with a poor sense
of the passage of time ?

Please use labels and text to provide additional information.

<a href="http://build.golang.org/log/5467657de567ee1ff619b30da43ef06871b2698c" rel="nofollow">http://build.golang.org/log/5467657de567ee1ff619b30da43ef06871b2698c</a>
<a href="http://build.golang.org/log/977d7ed62d3cc11c571832016b98020056523485" rel="nofollow">http://build.golang.org/log/977d7ed62d3cc11c571832016b98020056523485</a></pre>
<pre class="notranslate">What steps will reproduce the problem?

panic messages should list the go version (from runtime.theVersion) as well as the
operating system and arch details as close to the top of the panic message as possible. 

This would greatly aide in debugging problems reported on the mailing list and IRC as
those are the first details requested and the most often omitted.</pre>