[DO NOT MERGE] Run all PostCommit and PreCommit Tests against Release Branch

[lostluck]

Tests run on GHA should be queued shortly.

[github-actions]

Test Results

15 tests   15 ✅  1h 37m 40s ⏱️
12 suites   0 💤
12 files     0 ❌

Results for commit 85ed0d9.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[lostluck]

• PostCommit XVR GoUsingJava Dataflow - Permared ( low priority to investigate and fix. (The PostCommit XVR GoUsingJava Dataflow job is flaky #30519, and earlier with Fix failing "beam_PostCommit_XVR_GoUsingJava_Dataflow" job #28339), likely a docker push issue)
• XVR_Direct PostCommit 3.8 - (Other python versions passing, but times out after 2 hours. The PostCommit XVR Direct job is flaky #30517)
• PostCommit Java Examples Dataflow ARM - Flaky for Java 8 only (sometimes can't find symbols like, PCollection)) The PostCommit Java Examples Dataflow ARM job is flaky #31901
• PostCommit Python Arm - Flaky [Failing Test]: PostCommit Python and PostCommit Python Arm perma red #31203 (inconsistent with python versions)
• PostCommit Java IO Performance Tests - Permared The PostCommit Java IO Performance Tests job is flaky #30527 (Authentication errors from the looks of it)
• PostCommit Java PVR Spark Batch - (Flaky The PostCommit Java PVR Spark Batch job is flaky #30512)

[tvalentyn]

https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_Direct.yml?query=branch%3Amaster looks permared

[lostluck]

https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_Direct.yml?query=branch%3Amaster looks permared

Yup. That one is #30517

[tvalentyn]

Which of the errors above are a regression in 2.59.0 (if any) ?

[lostluck]

Which of the errors above are a regression in 2.59.0 (if any) ?

None of them, given the age of the root issues that I linked.