-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Publish Beam SDK Snapshots job is flaky #32161
Comments
Looking at https://github.com/apache/beam/actions/workflows/beam_Publish_Beam_SDK_Snapshots.yml this seems like it was a false positive, this has not been >80% flaky |
Reopening since the workflow is still flaky |
Reopening since the workflow is still flaky |
I confirm that it started to turn flaky again since Jan 15, 2025. |
@Amar3tto let us prioritize this. Thanks. |
could be blocked by gpu.org. |
I agree to try to optimize But it also fails for |
We can track the python failures here #33744 |
@shunping mentioned we could optimize I'm not sure how often licenses change, but it would be good to at least use the cache as a fall-back instead of failing after exhausting the retries |
.take-issue I am working on a PR to cache the licenses. |
The Publish Beam SDK Snapshots is failing over 80% of the time.
Please visit https://github.com/apache/beam/actions/workflows/beam_Publish_Beam_SDK_Snapshots.yml?query=is%3Afailure+branch%3Amaster to see all failed workflow runs.
See also Grafana statistics: http://metrics.beam.apache.org/d/CTYdoxP4z/ga-post-commits-status?orgId=1&viewPanel=1&var-Workflow=Publish%20Beam%20SDK%20Snapshots
The text was updated successfully, but these errors were encountered: