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

bigquery: TestIntegration_InsertErrors failed #4285

Closed
flaky-bot bot opened this issue Jun 18, 2021 · 2 comments · Fixed by #4280 or #4321
Closed

bigquery: TestIntegration_InsertErrors failed #4285

flaky-bot bot opened this issue Jun 18, 2021 · 2 comments · Fixed by #4280 or #4321
Assignees
Labels
api: bigquery Issues related to the BigQuery API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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 Jun 18, 2021

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


commit: 24c4451
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:1253: Wanted HTTP 400, got 413
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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 18, 2021
@product-auto-label product-auto-label bot added the api: bigquery Issues related to the BigQuery API. label Jun 18, 2021
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jun 18, 2021
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 18, 2021

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

gcf-merge-on-green bot pushed a commit that referenced this issue Jun 22, 2021
Context:  Looks like error mapping for excessively sized requests is
getting remapped to a more appropriate error code.  Change expectations
so we allow either HTTP 400 or 413 errors.

Fixes: #4277 
Fixes: #4279 
Fixes: #4285
@flaky-bot flaky-bot bot reopened this Jun 25, 2021
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 25, 2021

Oops! Looks like this issue is still flaky. It failed again. 😬

I reopened the issue, but a human will need to close it again.


commit: 267787e
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:1383: Error didn't contain expected message (Request payload size exceeds the limit): 

@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Jun 25, 2021
@shollyman shollyman 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. 🚨 This issue needs some love. labels Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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
2 participants