Skip to content

video.cloud-client.analyze.beta_snippets_test: test_annotation_to_storage_streaming failed #4636

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 Sep 5, 2020 · 4 comments
Assignees
Labels
api: videointelligence Issues related to the Video Intelligence API API. priority: p2 Moderately-important priority. Fix may not be included in 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 Sep 5, 2020

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


commit: 1c9244b
buildURL: Build Status, Sponge
status: failed

Test output
Traceback (most recent call last):
  File "/workspace/video/cloud-client/analyze/beta_snippets_test.py", line 60, in bucket
    bucket = storage_client.create_bucket(bucket_name)
  File "/workspace/video/cloud-client/analyze/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/storage/client.py", line 533, in create_bucket
    timeout=timeout,
  File "/workspace/video/cloud-client/analyze/.nox/py-3-7/lib/python3.7/site-packages/google/cloud/_http.py", line 423, in api_request
    raise exceptions.from_http_response(response)
google.api_core.exceptions.ServiceUnavailable: 503 POST https://storage.googleapis.com/storage/v1/b?project=python-docs-samples-tests: Backend Error
@flaky-bot flaky-bot bot added buildcop: issue 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 Sep 5, 2020
@product-auto-label product-auto-label bot added api: videointelligence Issues related to the Video Intelligence API API. samples Issues that are directly related to samples. labels Sep 5, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented Sep 5, 2020

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

@tmatsuo
Copy link
Contributor

tmatsuo commented Sep 8, 2020

#4644 will auto assign issues labeled api: videointelligence correctly.

@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Sep 12, 2020
@tmatsuo tmatsuo added the blunderbuss: assign Instruct blunderbuss to assign someone label Sep 14, 2020
@blunderbuss-gcf blunderbuss-gcf bot removed the blunderbuss: assign Instruct blunderbuss to assign someone label Sep 14, 2020
@tmatsuo
Copy link
Contributor

tmatsuo commented Sep 14, 2020

I think it's due to a flaky backend and not very serious. Downgrading to P2, but it is great if we can handle such a backend failure.

@tmatsuo tmatsuo added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed 🚨 This issue needs some love. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Sep 14, 2020
@telpirion
Copy link
Contributor

I'm closing this issue here so that we can consolidate all of the Python Video Intelligence issues within python-videointelligence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: videointelligence Issues related to the Video Intelligence API API. priority: p2 Moderately-important priority. Fix may not be included in 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

No branches or pull requests

4 participants