[Failing Test]: PostRelease Nightly Snapshot is perma-red due to "connect timed out"

What happened?

Seems like jar file resolution with Maven SNAPSHOT repo is somehow incorrect.

Successful run: https://github.com/apache/beam/actions/runs/11307102323/job/31448448902

[INFO] Archetype repository not defined. Using the one from [org.apache.beam:beam-sdks-java-maven-archetypes-examples:2.24.0] found in catalog remote
[INFO] Downloading from test.release: https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.61.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from test.release: https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.61.0-SNAPSHOT/maven-metadata.xml (1.7 kB at 3.3 kB/s)
[INFO] Downloading from test.release: https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.61.0-SNAPSHOT/beam-sdks-java-maven-archetypes-examples-2.61.0-20241012.122627-12.jar
[INFO] Downloaded from test.release: https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.61.0-SNAPSHOT/beam-sdks-java-maven-archetypes-examples-2.61.0-20241012.122627-12.jar (340 kB at 435 kB/s)

Failed run: https://github.com/apache/beam/actions/runs/11369820828/job/31628153369

[INFO] Archetype repository not defined. Using the one from [org.apache.beam:beam-sdks-java-maven-archetypes-examples:2.24.0] found in catalog remote
[INFO] Downloading from test.release: https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.61.0-SNAPSHOT/maven-metadata.xml
Warning:  Could not transfer metadata org.apache.beam:beam-sdks-java-maven-archetypes-examples:2.61.0-SNAPSHOT/maven-metadata.xml from/to test.release (https://repository.apache.org/content/repositories/snapshots): Connect to repository.apache.org:443 [repository.apache.org/65.109.119.155] failed: connect timed out
[INFO] Downloading from test.release: https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-maven-archetypes-examples/2.61.0-SNAPSHOT/beam-sdks-java-maven-archetypes-examples-2.61.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

Issue Failure

Failure: Test is flaky

Issue Priority

Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)

Issue Components

[ ] Component: Python SDK
[X] 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 warning message tells the reason:

Warning:  org.apache.beam:beam-runners-portability-java:2.61.0-SNAPSHOT/maven-metadata.xml failed to transfer from
https://repository.apache.org/content/repositories/snapshots during a previous attempt. This failure was cached in the
local repository and resolution will not be reattempted until the update interval of test.release has elapsed or updates are
forced. Original error: Could not transfer metadata org.apache.beam:beam-runners-portability-java:2.61.0-SNAPSHOT/maven-metadata.xml
from/to test.release (https://repository.apache.org/content/repositories/snapshots): Connect to
repository.apache.org:443 [repository.apache.org/65.109.119.155] failed: connect timed out

In particular,

This failure was cached in the local repository and resolution will not be reattempted until the update interval of test.release has elapsed or updates are forced.

Did some search: https://stackoverflow.com/questions/4856307/when-maven-says-resolution-will-not-be-reattempted-until-the-update-interval-of

what happens appear to be there was a run introduced bad local artifact, then in next a few days same artifact stays bad, until the "update interval" elapsed.

Noticed this also happened 3 weeks ago and after 6 run it recovered itself.

An action could be add "-U" flag in the mvn invocation.

apache / beam