Skip to content

ci(reborn): retry crates.io network failures in the closure (CARGO_NET_RETRY) #5115

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
serrrfirat merged 1 commit into from
Jun 21, 2026
Merged

ci(reborn): retry crates.io network failures in the closure (CARGO_NET_RETRY) #5115

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/workflows/reborn-tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,13 @@ env:
RUSTFLAGS: "-C linker=clang -C link-arg=--ld-path=/usr/bin/mold"
CARGO_PROFILE_DEV_DEBUG: 0
CARGO_PROFILE_TEST_DEBUG: 0
# The 64-crate closure runs ~64 jobs that each resolve+download the dependency
# tree from crates.io in parallel, so a transient registry SSL/HTTP2 hiccup
# (e.g. "download of <crate> failed: curl [55] SSL_ERROR_SYSCALL") tends to hit
# many jobs at once and redden the whole run. Make Cargo retry network failures
# (default 3) far more aggressively, and use the git CLI for git deps.
CARGO_NET_RETRY: "10"
CARGO_NET_GIT_FETCH_WITH_CLI: "true"

jobs:
changes:
Expand Down
Loading