-
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
[Bug]: PostRelease Nightly workflow flaky for release candidate validation #32808
Comments
Did something change recently ? For example, did we start running more tests that use the staging repository ? |
Ah, seems like it's just trying to get a non-existent file ? |
Seems like file-resolution is somehow incorrect. Successful run: https://github.com/apache/beam/actions/runs/11307102323/job/31448448902
Failed run: https://github.com/apache/beam/actions/runs/11369820828/job/31628153369
|
Filed #32824 for the HEAD failure. |
What happened?
Example run: https://github.com/apache/beam/actions/runs/11352551723
Failed with dependency resolution involving maven staging repository
the particular test targeted succeeded locally. It is likely due to that maven staging repository has less availability than maven central, and while, while multiple test target running in parallel, maven become flaky.
One possible fix is to force gradle targets run sequentially when the workflow is using maven staging repository
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: