Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.4.6, 3.0.0, 3.1.0
-
None
-
None
Description
Given the series of failures in Spark packaging Jenkins job, it seems that there is a network issue in AmbLab Jenkins cluster.
- The node failed to talk to GitBox. (
SPARK-31687) -> GitHub is okay. - The node failed to download the maven mirror. (
SPARK-31691) -> The primary host is okay. - The node failed to communicate repository.apache.org. (Current master branch Jenkins job failure)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) on project spark-parent_2.12: ArtifactDeployerException: Failed to retrieve remote metadata org.apache.spark:spark-parent_2.12:3.1.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata org.apache.spark:spark-parent_2.12:3.1.0-SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Transfer failed for https://repository.apache.org/content/repositories/snapshots/org/apache/spark/spark-parent_2.12/3.1.0-SNAPSHOT/maven-metadata.xml: Connect to repository.apache.org:443 [repository.apache.org/207.244.88.140] failed: Connection timed out (Connection timed out) -> [Help 1]
Attachments
Issue Links
- relates to
-
SPARK-31687 Use GitHub instead of GitBox in release script
- Resolved
-
SPARK-31691 release-build.sh should ignore a fallback output from `build/mvn`
- Resolved
-
SPARK-31713 Make test-dependencies.sh detect version string correctly
- Resolved