We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I just noticed this in https://source.cloud.google.com/results/invocations/d1a9e995-2251-4c81-b0c5-20c5b6b87a5d/targets/tests/tests;group=logging;test=TestLogsAndDelete;row=1 originally from https://source.cloud.google.com/results/invocations/60e6edc6-d114-4400-9020-62236f37ab9e/targets/cloud-go-libraries%2Fgoogle-cloud-go%2Fcontinuous%2Fmaster/log
logging_test.go:497: deleting "GO-LOGGING-CLIENT/TEST-LOG-20190919-73553409892752-0001": rpc error: code = ResourceExhausted desc = Quota exceeded for quota metric 'logging.googleapis.com/control_requests' and limit 'ControlRequestsPerMinutePerProject' of service 'logging.googleapis.com' for consumer 'project_number:36639933145'.
@jadekler @broady could we perhaps take a look at the quota limits and perhaps bump them up?
That Kokoro run identified a whole bunch of other flakes
The text was updated successfully, but these errors were encountered:
Looks like the quota is already maxed out:
I think we can request a quota bump separately. Should also consider using a project pool (see gimmeproj in golang-samples)
Sorry, something went wrong.
Will be fixed under #1654
freelerobot
No branches or pull requests
I just noticed this in https://source.cloud.google.com/results/invocations/d1a9e995-2251-4c81-b0c5-20c5b6b87a5d/targets/tests/tests;group=logging;test=TestLogsAndDelete;row=1 originally from https://source.cloud.google.com/results/invocations/60e6edc6-d114-4400-9020-62236f37ab9e/targets/cloud-go-libraries%2Fgoogle-cloud-go%2Fcontinuous%2Fmaster/log
@jadekler @broady could we perhaps take a look at the quota limits and perhaps bump them up?
That Kokoro run identified a whole bunch of other flakes
The text was updated successfully, but these errors were encountered: