error-reporting: Should correctly publish an error that is null failed
flaky-bot opened this issue · 1 comments
flaky-bot commented
Note: #671 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: b13cc6d
buildURL: Build Status, Sponge
status: failed
Test output
Timeout of 1200000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/workspace/build/system-test/error-reporting.js) Error: Timeout of 1200000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/workspace/build/system-test/error-reporting.js) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)
flaky-bot commented
Looks like this issue is flaky.
I'm going to leave this open and stop commenting.
A human should fix and close this.
When run at the same commit (b13cc6d), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).