youngoli commented on PR #17259: URL: https://github.com/apache/beam/pull/17259#issuecomment-1088296495
Logging my triaging on all the failing targets for transparency. Non-release blocking failures: [CommunityMetrics](https://ci-beam.apache.org/job/beam_PreCommit_CommunityMetrics_Phrase/121/) - Problem in our test infrastructure preventing metrics from being uploaded. Unrelated to Beam itself. [Google Cloud Dataflow Portability Runner Examples Java 11](https://ci-beam.apache.org/job/beam_PostCommit_Java11_Examples_Dataflow_Portability_PR/1/) - False negative. The build is successful but no tests are run and Jenkins reports that as a failure. [Google Cloud Dataflow Runner V2 Examples](Google Cloud Dataflow Runner V2 Examples) - False negative, same as above. [Java Flink PortableValidatesRunner Streaming Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming_PR/371/) - Only error has apparently been failing since being added, which is not a significant regression and therefore not release-blocking. [BEAM-14254](https://issues.apache.org/jira/browse/BEAM-14254) [Java Samza PortableValidatesRunner Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_PVR_Samza_PR/37/) - Only failure is the same as the Flink one above, and it's because Samza doesn't support the feature being tested. [Python 3.7 PostCommit](https://ci-beam.apache.org/job/beam_PostCommit_Python37_PR/340/) - Almost certainly a test configuration error and probably a flake. Failing to connect to a bigquery table. I'll be trying to deflake this just in case. [PythonDocs PreCommit](https://ci-beam.apache.org/job/beam_PreCommit_PythonDocs_Phrase/48/) - Fixed by #17176, I missed that during cherrypicks. Easy fix. Further investigation needed: [Dataflow Java Post Commit Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV1_PR/84/) - Many failures. Most seem likely to be non-release blocking, but still looking into it. [BEAM-14252](https://issues.apache.org/jira/browse/BEAM-14252) [Dataflow V2 Java Post Commit Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2_PR/88/) - Fewer failures than above, but some are identical failures and covered by the JIRA above. Then there's two spanner test failures that seem to be due to an incorrect config. Finally, one potentially problematic failure that I need to investigate further. [Link](https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2_PR/88/testReport/junit/org.apache.beam.sdk.io.gcp.bigquery/BigQueryIOStorageWriteIT/testBigQueryStorageWrite30MProto/) [JPMS Java 11 Dataflow Post Commit Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_Jpms_Dataflow_Java11_PR/9/) and [JPMS Java 17 Dataflow Post Commit Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_Jpms_Dataflow_Java17_PR/10/) - Failing due to lack of Dataflow worker container for 2.38.0. Will need to rerun once it's available. [Java PreCommit](https://ci-beam.apache.org/job/beam_PreCommit_Java_Phrase/4882/) - Been constantly timing out recently and being very flaky. Will need to keep rerunning until it doesn't timeout to see if it's actually failing or not. [Java SDK Post Commit Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_PR/1008/) - Same failures as the [Dataflow Java Post Commit Tests](https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV1_PR/84/), so investigating [BEAM-14252](https://issues.apache.org/jira/browse/BEAM-14252) will cover this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
