Repository navigation
Common Service: should retry a request failed #7343
Copy link
Copy link
Closed
googleapis/nodejs-storage
#2652Closed
Copy link
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.flakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.library: storageIssues transferred from another repositoryIssues transferred from another repositorypriority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Activity
- addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.
on Sep 11, 2025 - addedapi: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
on Sep 11, 2025 - addedflakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.
on Sep 12, 2025 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 (3a2ade8343911e628d2e061fd04f596f3755e30d), 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. 😬
I reopened the issue, but a human will need to close it again.
commit: b38b5d221f2cb72658c1eb4a726315ab395a542c
buildURL: Build Status, Sponge
status: failed- addedlibrary: storageIssues transferred from another repositoryIssues transferred from another repository
on Mar 3, 2026
Metadata
Metadata
Assignees
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.flakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.library: storageIssues transferred from another repositoryIssues transferred from another repositorypriority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Note: googleapis/nodejs-storage#2238 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 3a2ade8343911e628d2e061fd04f596f3755e30d
buildURL: Build Status, Sponge
status: failed