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

[Amar3tto]

Tests run on GHA should be queued shortly.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a configuration file designed to initiate a comprehensive suite of automated tests. The primary goal is to ensure stability and verify the integrity of the release branch by running both pre-commit and post-commit validation workflows via GitHub Actions.

Highlights

• Test Automation: Added a new configuration file to trigger the execution of all PostCommit and PreCommit tests against the release branch.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Test Results

15 tests +14 15 ✅ +14 1h 46m 11s ⏱️ + 1h 21m 35s
12 suites +11 0 💤 ± 0 
12 files +11 0 ❌ ± 0 

Results for commit b0495f8. ± Comparison against base commit b0872da.

♻️ This comment has been updated with latest results.

[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

[Amar3tto]

beam_PostCommit_Java_BigQueryEarlyRollout
StorageApiSinkRowUpdateIT > testCdcUsingLongSeqNum FAILED org.apache.beam.sdk.Pipeline$PipelineExecutionException at StorageApiSinkRowUpdateIT.java:205 Caused by: java.lang.RuntimeException at StorageApiWriteUnshardedRecords.java:857 Caused by: com.google.cloud.bigquery.storage.v1.Exceptions$StreamWriterClosedException at

[tvalentyn]

could you please rerun tests that fail/didn't run ?
for faliures, let's comment why they should not be blocking the release.

[github-actions]

Assigning reviewers:

R: @Abacn for label build.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[Amar3tto]

IcebergIO Managed Integration Tests on Dataflow and PostCommit Java ValidatesRunner Dataflow Streaming are failing on master.
PostCommit Python Arm and PostCommit Python Xlang Gcp Dataflow - timeout is too short.
PreCommit Java Clickhouse - Cherrypick: #38274

[tvalentyn]

Thanks

#34809 and #33721 are failing on master.

IIRC this was the release blocker and reason for RC2 - so tests failing on master doesn't justify that the error should be ignored.

PostCommit Python Arm and PostCommit Python Xlang Gcp Dataflow - timeout is too short.

Is there a tracking bug? when did it become too short? is it a regression of some sort?

Let's rerun the tests on the new RC. Thanks!

[Amar3tto]

IcebergIO - reason that we can skip

[Amar3tto]

Java ValidatesRunner - comment

[Amar3tto]

PythonArm - passed with increased timeout. Reason is a new Python 3.14 version

[Amar3tto]

Xlang also passed with increased timeout: https://github.com/apache/beam/actions/runs/25052637554

[Amar3tto]

Java Clickhouse: we decided that cherrypick is not needed, because the issue is only with workflow file change on master

@tvalentyn PTAL at my latest comments

[damccorm]

Let's rerun the tests on the new RC. Thanks!

I think this did happen, tests were retriggered on the new RC when the force push happened earlier in this PR.

With that said, we should make sure we're addressing all comments and giving time to respond before closing voting on the thread