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.

Sign up for GitHub

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

Jump to bottom

monitoring.api.v3.alerts-client.snippets_test: test_enable_alert_policies failed #3558

Closed
flaky-bot bot opened this issue Apr 27, 2020 · 3 comments
Closed

monitoring.api.v3.alerts-client.snippets_test: test_enable_alert_policies failed #3558

flaky-bot bot opened this issue Apr 27, 2020 · 3 comments
Assignees
@tmatsuo @busunkim96
Labels
priority: p2 Moderately-important priority. Fix may not be included in 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 Apr 27, 2020

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

commit: 2b74710
buildURL: Build Status, Sponge
status: failed
@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 Apr 27, 2020
@tmatsuo tmatsuo assigned tmatsuo and unassigned leahecole Apr 27, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 28, 2020

commit: 678f566
buildURL: Build Status, Sponge
status: failed

@tmatsuo tmatsuo added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Apr 28, 2020
@tmatsuo
Copy link
Contributor

tmatsuo commented Apr 28, 2020 •
edited
Loading

Error: google.api_core.exceptions.Aborted: 409 Too many concurrent edits to the project configuration. Please try again.

This will be easily fixed by using multiple projects, but considering that we're in the process of moving out some samples into client library repositories, we decided not to enable multiple projects in a near future (we may still use multiple projects on the client library repo).

There's no action items w.r.t this repository, so downgrading to P2.

@tmatsuo
Copy link
Contributor

tmatsuo commented May 1, 2020

We started to run the periodic builds with significant interval between them, so let me close this for now and let's see how often we see this failure.

@tmatsuo tmatsuo closed this as completed May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tmatsuo tmatsuo

@busunkim96 busunkim96

Labels
priority: p2 Moderately-important priority. Fix may not be included in 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
3 participants
@tmatsuo @leahecole @busunkim96