Thanks Vitaly and team! Its great to see the progress; anecdotally, it has also been nice to not have a bunch of flakes on most PRs :)
On Tue, Mar 4, 2025 at 11:03 AM Vitaly Terentyev via dev < dev@beam.apache.org> wrote: > Dear Community, > > Our team has been actively monitoring and improving Beam’s Infrastructure > & Health. In February, we focused on stabilizing flaky workflows, updating > performance metrics, and enhancing automation processes. As a result, with > most flaky tests resolved, the overall health level now exceeds 98%. Please > see the attached chart for February's Health Status trends. > > Key Improvements: > > - > > Flaky Test Fixes > - > > Resolved instability in multiple workflows, including LoadTests, > PreCommit and PostCommit jobs, snapshot releases and issue management > workflows. > - > > You can find the full list of closed or fixed 23 issues here > > <https://github.com/apache/beam/issues?q=is%3Aissue%20state%3Aclosed%20label%3Aflaky_test%20closed%3A%3E2025-02-01%20%20closed%3A%3C2025-02-28%20(involves%3AAmar3tto%20OR%20involves%3Aakashorabek)%20> > . > - > > Performance Metrics Update > - > > Updated Performance Metrics graphs on the Beam website > <https://beam.apache.org/performance/> using Looker-generated > images up to Beam 2.63.0. > - > > Automated > > <https://github.com/apache/beam/actions/workflows/refresh_looker_metrics.yml> > weekly updates of performance graphs provide real-time insights. > > Currently failing workflows > > - > > Important Signals (1) > - > > PostCommit Java Dataflow V2 > <https://github.com/apache/beam/issues/30729> > - > > Core Java Tests (1) > - > > PostCommit Java IO Performance Tests > <https://github.com/apache/beam/issues/30527> > - > > Dataflow Java Tests (1) > - > > PostCommit XVR GoUsingJava Dataflow > <https://github.com/apache/beam/issues/30519> > - > > Python Runners Tests (1) > - > > PostCommit Python ValidatesContainer Dataflow With RC > <https://github.com/apache/beam/issues/30525> > - > > Misc Tests (1) > - > > IcebergIO Integration Tests > <https://github.com/apache/beam/issues/31931> > > Ongoing and Future Work > > Our goal is to maintain this level of stability while proactively > addressing new issues. Additionally, we plan to migrate the Grafana > dashboard to https://metrics.beam.apache.org/ for better accessibility > and long-term maintenance. > > We will continue providing monthly updates to keep the community informed. > If you encounter any infrastructure-related issues, feel free to open a > GitHub issue with the label “infra > <https://github.com/apache/beam/issues?q=is%3Aissue%20state%3Aopen%20label%3Ainfra>”, > and our team will triage and resolve it. > > We appreciate your feedback and support in strengthening Beam’s > infrastructure. > Best regards, > Vitaly Terentyev > Akvelon Inc. > Apache Beam Infrastructure Team > >
