Closed bstoll closed 1 year ago
Yes, these have been flaky quite a bit. I've been meaning to flag it. Thank you for filing the issue
Still seeing similar errors:
=== RUN TestAwait/Too_slow/AwaitFor
check_test.go:268: Error [/parent/child/state/two: context deadline exceeded]:
Missing substring "wrong"
Missing substring "correct"
=== RUN TestAwait/Too_slow/AwaitUntil
check_test.go:279: Error [/parent/child/state/two: context deadline exceeded]:
Missing substring "wrong"
Missing substring "correct"
=== RUN TestAwait/Too_slow/multiple_values/AwaitFor
check_test.go:268: Error [/parent/child/state/two: context deadline exceeded]:
Missing substring "wrong2"
Missing substring "correct"
=== RUN TestAwait/Too_slow/multiple_values/AwaitUntil
check_test.go:279: Error [/parent/child/state/two: context deadline exceeded]:
Missing substring "wrong2"
Missing substring "correct"
=== RUN TestAwait/EOF_before_any_value/AwaitFor
E0731 23:54:20.177124 3558 client.go:226] Client error: end of updates
E0731 23:54:20.177642 3558 client.go:226] Client error: end of updates
=== RUN TestAwait/EOF_before_any_value/AwaitUntil
E0731 23:54:20.178142 3558 client.go:226] Client error: end of updates
E0731 23:54:20.178538 3558 client.go:226] Client error: end of updates
--- FAIL: TestAwait (2.01s)
--- PASS: TestAwait/Immediately_correct/AwaitFor (0.00s)
--- PASS: TestAwait/Immediately_correct/AwaitUntil (0.00s)
--- PASS: TestAwait/Delayed_correct/AwaitFor (0.00s)
--- PASS: TestAwait/Delayed_correct/AwaitUntil (0.00s)
--- FAIL: TestAwait/Too_slow/AwaitFor (0.50s)
--- FAIL: TestAwait/Too_slow/AwaitUntil (0.50s)
--- FAIL: TestAwait/Too_slow/multiple_values/AwaitFor (0.50s)
--- FAIL: TestAwait/Too_slow/multiple_values/AwaitUntil (0.50s)
--- PASS: TestAwait/EOF_before_any_value/AwaitFor (0.00s)
--- PASS: TestAwait/EOF_before_any_value/AwaitUntil (0.00s)
in #1961. Need to figure out if there is a better way to address this issue.
I missed @greg-dennis's followup commit updated the isTimeout check in #1961 that should have addressed this test failure.
1755 saw a bug where 'go test' CI check reported a failure. A followup rerun passed. Need to investigate how/why this check is flaky.
Log of failure: