Skip to content
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

dlp.inspect_content_test: test_inspect_gcs_image_file failed #3997

Closed
flaky-bot bot opened this issue Jun 6, 2020 · 1 comment · Fixed by #3959
Closed

dlp.inspect_content_test: test_inspect_gcs_image_file failed #3997

flaky-bot bot opened this issue Jun 6, 2020 · 1 comment · Fixed by #3959
Assignees
Labels
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 Jun 6, 2020

This test failed!

To configure my behavior, see the Build Cop Bot documentation.

If I'm commenting on this issue too often, add the buildcop: quiet label and
I will stop commenting.


commit: 6b5f855
buildURL: Build Status, Sponge
status: failed

Test output
Traceback (most recent call last):
  File "/workspace/dlp/inspect_content_test.py", line 380, in test_inspect_gcs_image_file
    assert "Info type: EMAIL_ADDRESS" in out
AssertionError: assert 'Info type: EMAIL_ADDRESS' in 'Inspection operation started: projects/python-docs-samples-tests/locations/global/dlpJobs/i-492004000233460469\nNo event received before the timeout. Please verify that the subscription provided is subscribed to the topic provided.\n'
@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 Jun 6, 2020
@tmatsuo tmatsuo assigned tmatsuo and unassigned busunkim96 Jun 6, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 8, 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 (6b5f855), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Development

Successfully merging a pull request may close this issue.

2 participants