Thank you for the update, great work! On Mon, Feb 17, 2025 at 7:31 AM Vitaly Terentyev via dev < dev@beam.apache.org> wrote:
> Dear Community, > Our team has been actively monitoring and improving Beam’s Infrastructure > & Health. During the last month, we focused on fixing flaky and permared > workflows, successfully resolving multiple issues, and enhancing overall > system stability. > *Key Improvements:* > > 1. *Stabilization of Workflows* > - *Workflow Stabilization:* Resolved issues across Go LoadTests, Kafka > IO Performance Tests, Java IOs Direct PreCommit, Python Examples > PostCommit > Jobs, xlang KafkaIO Python Performance Tests, and Java ValidatesRunner > Jobs. > - *Dependency and Environment Adjustments:* > 1. Reverted specific dependency versions > 2. Updated OS environments for Python jobs (e.g., migrated to > Ubuntu 22.04) > 3. Temporarily shifted jobs to GitHub-hosted runners. > - Additionally, over 10 issues related to flaky tests were > closed or fixed, see details > > <https://github.com/apache/beam/issues?q=is%3Aissue%20state%3Aclosed%20label%3Aflaky_test%20closed%3A%3E2025-01-08%20%20closed%3A%3C2025-01-31%20(involves%3AAmar3tto%20OR%20involves%3Aakashorabek)%20> > here > > <https://github.com/apache/beam/issues?q=is%3Aissue%20state%3Aclosed%20label%3Aflaky_test%20closed%3A%3E2025-01-08%20%20closed%3A%3C2025-01-31%20(involves%3AAmar3tto%20OR%20involves%3Aakashorabek)%20> > . > 2. *Health Dashboard* > We started tracking daily metrics for each Beam component, including the > number and types of new and resolved issues. The dashboard provides both > overall repository health status and health percentages for each Beam > component. Beam Health Trends are calculated based on the ratio of stable > GitHub workflows to the total number of workflows, considering open issues > labeled “*flaky_test”*. All workflow runs can be monitored in the > <http://35.193.202.176/d/CTYdoxP4z/ga-post-commits-status?orgId=1>Grafana > dashboard > <http://35.193.202.176/d/CTYdoxP4z/ga-post-commits-status?orgId=1>. > Please see the attached chart for January's Health Status trends. > > *Currently failing workflows:* > > - Important Signals (1) > - <https://github.com/apache/beam/issues/33722>PostCommit Java > ValidatesRunner Dataflow > <https://github.com/apache/beam/issues/33722> > - <https://github.com/apache/beam/issues/33720>PostCommit Java > ValidatesRunner Dataflow V2 > <https://github.com/apache/beam/issues/33720> > - <https://github.com/apache/beam/issues/30513>PostCommit Python > <https://github.com/apache/beam/issues/30513> > - Core Java Tests (2) > - <https://github.com/apache/beam/issues/33909>PreCommit Java GCP IO > Direct <https://github.com/apache/beam/issues/33909> > - <https://github.com/apache/beam/issues/30527>PostCommit Java IO > Performance Tests <https://github.com/apache/beam/issues/30527> > - Dataflow Java Tests (2) > - <https://github.com/apache/beam/issues/30519>PostCommit XVR > GoUsingJava Dataflow <https://github.com/apache/beam/issues/30519> > - <https://github.com/apache/beam/issues/30606>PostCommit Java > Nexmark Dataflow <https://github.com/apache/beam/issues/30606> > - <https://github.com/apache/beam/issues/33723>PostCommit Java > ValidatesRunner Dataflow JavaVersions > <https://github.com/apache/beam/issues/33723> > - Python Runners Tests (2) > - <https://github.com/apache/beam/issues/30525>PostCommit Python > ValidatesContainer Dataflow With RC > <https://github.com/apache/beam/issues/30525> > - <https://github.com/apache/beam/issues/33065>Python > ValidatesContainer Dataflow ARM > <https://github.com/apache/beam/issues/33065> > - Go Tests (2) > - <https://github.com/apache/beam/issues/30507>LoadTests Go GBK Flink > Batch <https://github.com/apache/beam/issues/30507> > - <https://github.com/apache/beam/issues/30502>LoadTests Go CoGBK > Flink Batch <https://github.com/apache/beam/issues/30502> > - Miscs Tests (3) > - <https://github.com/apache/beam/issues/33698>finalize_release > <https://github.com/apache/beam/issues/33698> > - <https://github.com/apache/beam/issues/31931>IcebergIO > Integration Tests <https://github.com/apache/beam/issues/31931> > - <https://github.com/apache/beam/issues/30505>PostRelease Nightly > Snapshot <https://github.com/apache/beam/issues/30505> > > *Ongoing and Future Work* > We are actively addressing issues and targeting the root causes of > recurring errors. Going forward, we will provide monthly updates to keep > you informed. Additionally, if you encounter any infrastructure-related > issues, feel free to open a GitHub issue with the label “ > <https://github.com/apache/beam/issues?q=is%3Aissue%20state%3Aopen%20label%3Ainfra> > infra > <https://github.com/apache/beam/issues?q=is%3Aissue%20state%3Aopen%20label%3Ainfra>”, > and our team will triage and address it. We appreciate your feedback and > use it to strengthen Beam's infrastructure. > > Best regards, > Vitaly Terentyev > Akvelon Inc. > Apache Beam Infrastructure Team > >
