Skip to content

data-science-onramp.data-ingestion.ingestion_test: test_setup failed #10228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
flaky-bot bot opened this issue Jun 13, 2023 · 2 comments · Fixed by #10258
Closed

data-science-onramp.data-ingestion.ingestion_test: test_setup failed #10228

flaky-bot bot opened this issue Jun 13, 2023 · 2 comments · Fixed by #10258
Assignees
Labels
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. samples Issues that are directly related to samples. 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 Jun 13, 2023

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


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

Test output
Traceback (most recent call last):
  File "/workspace/data-science-onramp/data-ingestion/ingestion_test.py", line 90, in setup_and_teardown_cluster
    operation.result()
  File "/workspace/data-science-onramp/data-ingestion/.nox/py-3-10/lib/python3.10/site-packages/google/api_core/future/polling.py", line 261, in result
    raise self._exception
google.api_core.exceptions.InvalidArgument: 400 The resource 'projects/python-docs-samples-tests/regions/us-central1/subnetworks/default' is not ready
@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 Jun 13, 2023
@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Jun 13, 2023
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 14, 2023

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

@flaky-bot flaky-bot bot closed this as completed Jun 14, 2023
@flaky-bot flaky-bot bot reopened this Jun 15, 2023
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jun 15, 2023
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 15, 2023

Looks like this issue is flaky. 😟

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

A human should fix and close this.


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

Test output
Traceback (most recent call last):
  File "/workspace/data-science-onramp/data-ingestion/ingestion_test.py", line 90, in setup_and_teardown_cluster
    operation.result()
  File "/workspace/data-science-onramp/data-ingestion/.nox/py-3-10/lib/python3.10/site-packages/google/api_core/future/polling.py", line 261, in result
    raise self._exception
google.api_core.exceptions.InvalidArgument: 400 The resource 'projects/python-docs-samples-tests/regions/us-central1/subnetworks/default' is not ready 3: The resource 'projects/python-docs-samples-tests/regions/us-central1/subnetworks/default' is not ready

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. samples Issues that are directly related to samples. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants