error-reporting: Should correctly publish an error that is a number failed
Note: #700 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 3b763879091d5844dc5f46831680f202a7e79f14 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:557:17)
at processTimers (internal/timers.js:500:7)
Looks like this issue is flaky. :worried:
I'm going to leave this open and stop commenting.
A human should fix and close this.
When run at the same commit (3b763879091d5844dc5f46831680f202a7e79f14), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: 23e36857ab35d3b3dab2ca55713564677f48b4c9 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:557:17)
at processTimers (internal/timers.js:500:7)
Flaky test: https://btx-internal.corp.google.com/invocations;p=250644331956?q=target:cloud-devrel%2Fclient-libraries%2Fnodejs%2Fcontinuous%2Fgoogleapis%2Fnodejs-error-reporting%2Fnode14%2Fsystem-test