+1 (binding).

Checked the test suites (Thanks for following up Yi and Vitaly),
spot-checked  cloned Dataflow containers, verified that some of the changes
introduced late to the release branch made it to RC3.

On Mon, Oct 27, 2025 at 12:42 PM Yi Hu via dev <[email protected]> wrote:

> Thanks Valentyn for pointing out this issue.
>
> Had a closer look and a few reruns, commented to
> https://github.com/apache/beam/pull/36615#issuecomment-3452959418.
> Basically
>
> - The parallelism is uneven due to a few test classes contribute to most
> number of tests
>
> - Pipeline full lifecycle time has been elevated ub general, possibly due
> to more teardown time spend, that is not related to SDK
>
> - no single stuck test found
>
> I pushed another change to just run ViewTest (in
> https://github.com/apache/beam/pull/36634). We definitely should resolve
> these issues in main branch though it isn't release blocking
>
> Thanks,
>
> Yi
>
> On Thu, Oct 23, 2025 at 7:53 PM Valentyn Tymofieiev via dev <
> [email protected]> wrote:
>
>> I see that beam_PostCommit_Java_ValidatesRunner_Dataflow_V2_Streaming on
>> https://github.com/apache/beam/pull/36577 is timing out; i tried
>> rerunning it,  but my rerun was not successful, executions on master also
>> frequently timeout and take 8hr+ to run. This is an important suite to have
>> a green signal. Have we  investigated these timeouts somewhere?
>>
>> On Thu, Oct 23, 2025 at 11:00 AM Vitalii Terentev <[email protected]>
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Tested Python Mobile Gaming RC Validation [1], Go WordCount [2], Java
>>> QuickStart [3], Java Mobile Gaming [4], Dataflow templates [5].
>>>
>>> [1] https://github.com/apache/beam/actions/runs/18691423802
>>> [2] https://github.com/apache/beam/actions/runs/18691432479
>>> [3] https://github.com/apache/beam/actions/runs/18691412942
>>> [4] https://github.com/apache/beam/actions/runs/18691418290
>>> [5] https://github.com/GoogleCloudPlatform/DataflowTemplates/pull/2907
>>>
>>>
>>> On 2025/10/21 17:03:20 Vitaly Terentyev via dev wrote:
>>> > Hi everyone,
>>> > Please review and vote on the release candidate #3 for the version
>>> 2.69.0,
>>> > as follows:
>>> > [ ] +1, Approve the release
>>> > [ ] -1, Do not approve the release (please provide specific comments)
>>> >
>>> >
>>> > Reviewers are encouraged to test their own use cases with the release
>>> > candidate, and vote +1 if
>>> > no issues are found. Only PMC member votes will count towards the final
>>> > vote, but votes from all
>>> > community members are encouraged and helpful for finding regressions;
>>> you
>>> > can either test your own
>>> > use cases [13] or use cases from the validation sheet [10].
>>> >
>>> > The complete staging area is available for your review, which includes:
>>> > * GitHub Release notes [1],
>>> > * the official Apache source release to be deployed to dist.apache.org
>>> [2],
>>> > which is signed with the key with fingerprint D20316F712213422 as
>>> automated
>>> > [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.69.0-RC3" [5],
>>> > * website pull request listing the release [6], the blog post [6], and
>>> > publishing the API reference manual [7].
>>> > * Python artifacts are deployed along with the source release to
>>> > dist.apache.org [2] and PyPI[8].
>>> > * Go artifacts and documentation are available at pkg.go.dev [9]
>>> > * Validation sheet with a tab for 2.69.0 release to help with
>>> validation
>>> > [10].
>>> > * Docker images published to Docker Hub [11].
>>> > * PR to run tests against release branch [12].
>>> > * Github Release pre-release page for v2.69.0-RC3 [13].
>>> > * pull request to apache/beam updating the managed-io docs[15]
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by majority
>>> > approval, with at least 3 PMC affirmative votes.
>>> >
>>> > For guidelines on how to try the release in your projects, check out
>>> our RC
>>> > testing guide [14].
>>> >
>>> > Thanks,
>>> > Release Manager
>>> >
>>> > [1] https://github.com/apache/beam/milestone/37
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.69.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1416/
>>> > [5] https://github.com/apache/beam/tree/v2.69.0-RC3
>>> > [6] https://github.com/apache/beam/pull/36554
>>> > [7] https://github.com/apache/beam-site/pull/692
>>> > [8] https://pypi.org/project/apache-beam/2.69.0rc3/
>>> > [9]
>>> https://pkg.go.dev/github.com/apache/beam/sdks/[email protected]/go/pkg/beam
>>> > [10]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit?gid=1955791650#gid=1955791650
>>> > [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>>> > [12] <https://github.com/apache/beam/pull/36531>
>>> https://github.com/apache/beam/pull/36577
>>> > [13] https://github.com/apache/beam/releases/tag/v2.69.0-RC3
>>> > [14]
>>> https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md
>>> > [15] https://github.com/apache/beam/pull/36569
>>> >
>>>
>>

Reply via email to