afterincomparableyum opened a new pull request, #3877:
URL: https://github.com/apache/celeborn/pull/3877
build/sbt fetched sbt-launch.jar from repo1.maven.org with a single `curl
--silent` call and no retry. Any brief failure from Maven Central (DNS,
connection reset, 403/429 throttling) failed the whole CI job before a single
test ran, and the log never said why. The repo's Actions cache sits at its 10GB
limit, so the cached launcher is usually evicted and every SBT matrix job
downloads it at the same time.
Dependency resolution had the same weak point. build/sbt-config/repositories
lists Google's Maven Central mirror ahead of repo1, but at the old
/repos/central/data/ path, which now returns 404. Every artifact was really
fetched from repo1 alone, so a repo1 connection reset failed the build (e.g.
"could not retrieve sbt 1.9.4" when the launcher couldn't download
scala-reflect).
- Retry the launcher download with curl/wget, and add --retry-all-errors
when curl supports it (7.71+), because plain --retry skips DNS, connection and
403 errors.
- Print the download error instead of hiding it.
- If repo1 still fails, fetch the launcher from Google's Maven Central
mirror. Skip that fallback when DEFAULT_ARTIFACT_REPOSITORY is set, so builds
limited to an internal repo stay that way.
- Point gcs-maven-central-mirror at the live /maven2/ path, as
repositories-asia.template already does, so dependencies have a working mirror
ahead of repo1.
<!--
Thanks for sending a pull request! Here are some tips for you:
- Make sure the PR title start w/ a JIRA ticket, e.g. '[CELEBORN-XXXX]
Your PR title ...'.
- Be sure to keep the PR description updated to reflect all changes.
- Please write your PR title to summarize what this PR proposes.
- If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
### Why are the changes needed?
### Does this PR resolve a correctness bug?
<!-- Check if yes. The `correctness` label will be added/removed
automatically. -->
- [ ] Yes
### Does this PR introduce _any_ user-facing change?
<!-- Check if yes. -->
- [ ] Yes
### How was this patch tested?
--
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]
