apache / apache/beam

Retry downloading required test artifacts with a backoff when download fails.

Open
#18,565 0 comments 0 reactions 0 assignees View on GitHub
failing test improvement P3 tests
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
205

Description

When Maven fails to download a required artifact for a test, the test fails. Is it possible to configure Maven to retry the download with a backoff up to N number of attempts?

Example test failure:
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15004/console

2017-10-11T19:01:21.382 [INFO] \--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--
2017-10-11T19:01:21.382 [INFO] BUILD FAILURE
2017-10-11T19:01:21.382 [INFO] \--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--
2017-10-11T19:01:21.383 [INFO] Total time: 55:20 min
2017-10-11T19:01:21.383 [INFO] Finished at: 2017-10-11T19:01:21****00:00
2017-10-11T19:01:23.807 [INFO] Final Memory: 261M/2068M
2017-10-11T19:01:23.807 [INFO] \--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--\--
2017-10-11T19:01:23.836 [ERROR] Failed to execute goal on project beam-sdks-java-io-hcatalog: Could not resolve dependencies for project org.apache.beam:beam-sdks-java-io-hcatalog:jar:2.2.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.hive:hive-metastore:jar:2.1.0, javolution:javolution:jar:5.5.1: Could not transfer artifact org.apache.hive:hive-metastore:jar:2.1.0 from/to central (https://repo.maven.apache.org/maven2): GET request of: org/apache/hive/hive-metastore/2.1.0/hive-metastore-2.1.0.jar from central failed: Connection reset -\> [Help 1].

Imported from Jira [BEAM-3055](https://issues.apache.org/jira/browse/BEAM-3055). Original Jira may contain additional context.
Reported by: tvalentyn.

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by inspecting the Beam Maven build and the Jenkins failure linked in the issue to find where required test artifacts are downloaded. Done means transient download failures retry up to a configured limit with backoff and the affected test build succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.