Skip to content

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

Closed

Description

@flaky-bot

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


commit: 6681669
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-9/lib/python3.9/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

Activity

  1. added
    flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.
    priority: p1Important 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.
    on Apr 24, 2023
  2. flaky-bot commented on Apr 24, 2023

    @flaky-bot
    Author

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

  3. added
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Apr 24, 2023
  4. leahecole commented on May 4, 2023

    @leahecole
    Collaborator

    This is decorated with the internal api_core retry instead of backoff which doesn't allow us to dictate how many times it retries. if it fails again, I think we should make it match the other dataproc tests with backoff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

flakybot: flakyTells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.samplesIssues that are directly related to samples.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions