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
Since midnight of March 22: https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2/2826/testReport/junit/org.apache.beam.sdk.io.gcp.bigquery/BigQueryIOStorageWriteIT/testBigQueryStorageWrite30MProtoALO/
There is one BigQuery Storage Write change at that time: #25723
Failure: Test is continually failing
Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)
The text was updated successfully, but these errors were encountered:
CC: @reuvenlax @jrmccluskey adding to the milestone of v2.47.0 since the release cut is soon
Sorry, something went wrong.
related: due to #25851 the test is red for a while which may have caused that this issue not discovered quickly. Opened #26060
Successfully merging a pull request may close this issue.
What happened?
Since midnight of March 22: https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2/2826/testReport/junit/org.apache.beam.sdk.io.gcp.bigquery/BigQueryIOStorageWriteIT/testBigQueryStorageWrite30MProtoALO/
There is one BigQuery Storage Write change at that time: #25723
Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)
Issue Components
The text was updated successfully, but these errors were encountered: