Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

create start instance tests: should create instance with subnet failed #755

Closed
flaky-bot bot opened this issue Jul 9, 2022 · 1 comment
Closed

create start instance tests: should create instance with subnet failed #755

flaky-bot bot opened this issue Jul 9, 2022 · 1 comment
Labels
api: compute Issues related to the googleapis/nodejs-compute API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Jul 9, 2022

Note: #722 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

commit: 8ff77f6
buildURL: Build Status, Sponge
status: failed

Test output
Command failed: node instances/create-start-instance/createInstanceWithSubnet long-door-651 europe-central2-b gcloud-test--cd6471b7-5341-434 global/networks/default-compute regions/europe-central2/subnetworks/default-compute
The resource 'projects/long-door-651/zones/europe-central2-b/instances/gcloud-test--cd6471b7-5341-434' already exists

Error: Command failed: node instances/create-start-instance/createInstanceWithSubnet long-door-651 europe-central2-b gcloud-test--cd6471b7-5341-434 global/networks/default-compute regions/europe-central2/subnetworks/default-compute

The resource 'projects/long-door-651/zones/europe-central2-b/instances/gcloud-test--cd6471b7-5341-434' already exists


at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (test/createStartInstance.test.js:31:28)
at Context.<anonymous> (test/createStartInstance.test.js:219:20)</pre></details>
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Jul 9, 2022
@product-auto-label product-auto-label bot added the api: compute Issues related to the googleapis/nodejs-compute API. label Jul 9, 2022
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jul 10, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Jul 10, 2022

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 (8ff77f6), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@sofisl sofisl mentioned this issue Jul 12, 2022
Merged
@sofisl sofisl closed this as completed Jul 13, 2022
@flaky-bot flaky-bot bot mentioned this issue Sep 17, 2022
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
api: compute Issues related to the googleapis/nodejs-compute API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sofisl