asset/quickstart/export-assets-bigquery: TestMain failed
Note: #2642 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 4226690ccc343022b414ac38faa39a0a3550929f buildURL: Build Status, Sponge status: failed
Test output
retry.go:44: FAILED after 10 attempts:
main_test.go:46: error running main: exit status 1:
2023/01/25 20:17:19 ExportAssets: rpc error: code = InvalidArgument desc = Request contains an invalid argument.</pre></details>
Looks like this issue is flaky. :worried:
I'm going to leave this open and stop commenting.
A human should fix and close this.
When run at the same commit (4226690ccc343022b414ac38faa39a0a3550929f), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).
Closing, since this issue has not occurred in several months. Can investigate if it happens again.
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: bab3cb016648f4a4c36c13465f9bdc7d39f7957b buildURL: Build Status, Sponge status: failed
Test output
retry.go:44: FAILED after 10 attempts:
main_test.go:46: error running main: exit status 1:
2023/05/18 18:45:10 ExportAssets: rpc error: code = InvalidArgument desc = Request contains an invalid argument.</pre></details>
@angieshen-google Can someone from your team investigate why these tests are failling?
Closing per comment in the internal system. If this re-opens we will need to investigate further.
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: d0a922fc011981f6a472f047b88902b234d5e3ee buildURL: Build Status, Sponge status: failed
Test output
main_test.go:66: Dataset.Create("golang_samples_tests_7_for_assets"): googleapi: Error 409: Already Exists: Dataset golang-samples-tests-7:golang_samples_tests_7_for_assets, duplicate
ExportAssets API is owned by Asset Platform team, thus I reassigned the bug to their team and removed myself from assignee. Thanks!
One of the reasons this test is failing is that it uses a static collection name for the Dataset, creating resource contention.
I'll investigate making these less flaky, or we'll just skip them until the responsible team can fix them properly (and file an issue for the fix).
closing unaddressed flaky-bot:flaky issues, see go/flakybot-bankruptcy