search

googleapis / nodejs-storage

Node.js client for Google Cloud Storage: unified object storage for developers and enterprises, from live data serving to data analytics/ML to data archiving.
https://cloud.google.com/storage/
Apache License 2.0
898 stars 370 forks source link

storage notifications: should emit events to a subscription failed #2267

Closed flaky-bot[bot] closed 1 year ago

flaky-bot[bot] commented 1 year ago

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and I will stop commenting.

commit: 0c9b3425b47c3031ec4bac6d45d8cdca48b2f1a6 buildURL: Build Status, Sponge status: failed

Test output
Timeout of 600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/workspace/build/system-test/storage.js)
Error: Timeout of 600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/workspace/build/system-test/storage.js)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)
flaky-bot[bot] commented 1 year ago

Test passed for commit c881bae96b40f609d2b7a8d7388c6a76d34faab1 (Build Status, Sponge)! Closing this issue.

flaky-bot[bot] commented 1 year ago

Looks like this issue is flaky. :worried:

I'm going to leave this open and stop commenting.

A human should fix and close this.

commit: e0f45c24b44d11c72ff40cc534be11cb2a65192f buildURL: Build Status, Sponge status: failed

Test output
Timeout of 600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/workspace/build/system-test/storage.js)
Error: Timeout of 600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/workspace/build/system-test/storage.js)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)
ddelgrosso1 commented 1 year ago

This looks like a random network issue NOT related to gtoken / auth ECONNRESET. Going to close this.