You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.
Workaround:
./src/go/printer/printer_test.go: line 183
case <-time.After(1000 * time.Second): // plenty of a safety margin, even for very slow machines
The text was updated successfully, but these errors were encountered:
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
Testing
An issue that has been verified to require only test changes, not just a test failure.
labels
Jul 2, 2021
dmitshur
changed the title
absolute timing fails on slow devices and breaks test
go/printer: absolute timing fails on slow devices and breaks test
Jul 2, 2021
NeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
compile on raspberry pi:
What did you expect to see?
ALL TESTS PASSED
What did you see instead?
--- FAIL: TestFiles (0.00s)
--- FAIL: TestFiles/empty.input (10.01s)
printer_test.go:185: testdata/empty.input: running too slowly
--- FAIL: TestFiles/go2numbers.input#01 (10.01s)
printer_test.go:185: testdata/go2numbers.input: running too slowly
--- FAIL: TestFiles/go2numbers.input (10.01s)
printer_test.go:185: testdata/go2numbers.input: running too slowly
Workaround:
./src/go/printer/printer_test.go: line 183
case <-time.After(1000 * time.Second): // plenty of a safety margin, even for very slow machines
The text was updated successfully, but these errors were encountered: