-
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 PostRelease Nightly Snapshot job is flaky #30505
Comments
Related to ##30447 |
Still failing:
It is strange that the container gets resolved to "beam_java8_sdk:beam-master-20240306". What happens is it picks the label for legacy runner but actually trying to pull runner v2 image. This is likely due to Dataflow switched to runner v2 by default in Beam 2.55.0+ beam/runners/google-cloud-dataflow-java/build.gradle Lines 54 to 55 in ef919e2
entered #30634 |
https://github.com/apache/beam/actions/runs/8619063045
|
Looks much better. Close this now. |
Currently there is a flakiness due to downloading artifacts from maven snapshot repository not get retried. This is a maven tool thing, but probably we can first build (with retry) so the artifacts are get cached in local maven |
@shunping please check this when you have time. |
Related to the maven snapshot issue. I wonder if we could use artifact registry's ability to store Java packages https://cloud.google.com/artifact-registry/docs/java/store-java, instead of relying on maven central. |
|
Can we just add the retry to this task? |
Looking at some of the recent failures seems like Java command was just crashing ? https://github.com/apache/beam/actions/runs/9537373049/job/26285395593 "Process 'command '/opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/8.0.412-8/x64/bin/java'' finished with non-zero exit value 1" |
I also see the 404 error from BQ mentioned above in other failed runs, so seems like there are at least two failure modes. |
I wonder if Java failure was due to an OOM. Can we increase the memory available to VMs running these tests ? |
Trying this with #31749 |
Reopening since the workflow is still flaky |
Green now. |
The PostRelease Nightly Snapshot is failing over 50% of the time
Please visit https://github.com/apache/beam/actions/workflows/beam_PostRelease_NightlySnapshot.yml?query=is%3Afailure+branch%3Amaster to see the logs.
The text was updated successfully, but these errors were encountered: