Abacn opened a new issue, #32808: URL: https://github.com/apache/beam/issues/32808
### What happened? Example run: https://github.com/apache/beam/actions/runs/11352551723 Failed with dependency resolution involving maven staging repository ``` Failed to execute goal on project word-count-beam: Could not resolve dependencies for project org.example:word-count-beam:jar:0.1: Failed to collect dependencies at org.apache.beam:beam-runners-portability-java:jar:2.60.0: Failed to read artifact descriptor for org.apache.beam:beam-runners-portability-java:jar:2.60.0: The following artifacts could not be resolved: org.apache.beam:beam-runners-portability-java:pom:2.60.0 (absent): Could not transfer artifact org.apache.beam:beam-runners-portability-java:pom:2.60.0 from/to test.release (https://repository.apache.org/content/repositories/orgapachebeam-1387/): Connect to repository.apache.org:443 [repository.apache.org/65.109.119.155] failed: connect timed out -> [Help 1] ``` 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 - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
