In the PR I added some context on the persistently failing ones (none should be concerning) https://github.com/apache/beam/pull/37244#issuecomment-3724257442.
That includes all the failures which showed up in RC1/2. To your point, there are also some flaky suites. I did basic investigation for these, and most looked like test issues, not real problems so I retried during previous RCs and they went away. I forgot to retry the flakes in RC3 though, thanks for kicking off the retries. Thanks, Danny On Wed, Jan 21, 2026 at 11:34 AM Valentyn Tymofieiev via dev < [email protected]> wrote: > I am seeing some test failures on > https://github.com/apache/beam/pull/37244 . I reran all failed test > suites, looks like Go Postcommits failed again, and some suits are still > running. Have we investigated these errors? If so, it would be helpful to > call out on the PR tracking bugs or reasons that the failures are not > release-blocking. > > Thanks! > > > On Wed, Jan 21, 2026 at 12:33 AM Jan Lukavský <[email protected]> wrote: > >> +1 (binding) >> >> Tested Java SDK pipelines with Flink Runner. >> On 1/21/26 05:01, Derrick Williams via dev wrote: >> >> +1 (non-binding) >> >> Tested Yaml SDK with several yaml pipelines via DirectRunner, >> PrismRunner, and DataflowRunner. >> >> >> On Tue, Jan 20, 2026 at 5:14 PM Chamikara Jayalath via dev < >> [email protected]> wrote: >> >>> +1 (binding) >>> >>> Tested some pipelines that use multi-lang and managed transforms. >>> >>> Thanks, >>> Cham >>> >>> On Tue, Jan 20, 2026 at 2:08 PM Claudius van der Merwe < >>> [email protected]> wrote: >>> >>>> +1 (non-binding) - Ran a bunch of BigQueryIO read/write jobs. >>>> >>>> Claude >>>> >>>> On Sat, Jan 17, 2026 at 7:49 AM Danny McCormick via dev < >>>> [email protected]> wrote: >>>> >>>>> +1 (binding) - Ran a bunch of tests covered in >>>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit?gid=769555300#gid=769555300 >>>>> along >>>>> with an ML example and Dataflow Templates validation. Confirmed that we're >>>>> not running into the same bug as the previous RCs. >>>>> >>>>> Thanks, >>>>> Danny >>>>> >>>>> On Sat, Jan 17, 2026 at 6:56 AM Danny McCormick < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> Please review and vote on the release candidate #3 for the version >>>>>> 2.71.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 [3], >>>>>> * all artifacts to be deployed to the Maven Central Repository [4], >>>>>> * source code tag "v2.71.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.71.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.71.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 [13]. >>>>>> >>>>>> Thanks, >>>>>> Danny >>>>>> >>>>>> [1] https://github.com/apache/beam/milestone/39 >>>>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.71.0/ >>>>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS >>>>>> [4] >>>>>> https://repository.apache.org/content/repositories/orgapachebeam-1422/ >>>>>> [5] https://github.com/apache/beam/tree/v2.71.0-RC3 >>>>>> [6] https://github.com/apache/beam/pull/37256 >>>>>> [7] https://github.com/apache/beam-site/pull/699 >>>>>> [8] https://pypi.org/project/apache-beam/2.71.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=769555300#gid=769555300 >>>>>> [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image >>>>>> [12] https://github.com/apache/beam/pull/37244 >>>>>> [13] https://github.com/apache/beam/releases/tag/v2.71.0-RC3 >>>>>> [14] >>>>>> https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md >>>>>> [15] https://github.com/apache/beam/pull/37333 >>>>>> >>>>> >> >> -- >> >> Derrick Williams >> >> Software Engineer >> >> >>
