Skip to content

ci: make musl toolchain/zlib downloads resilient to musl.cc outages#148

Merged
rahlk merged 1 commit into
146-package-codeanalyzer-java-as-a-pypi-distribution-with-pypi-releaseymlfrom
fix/pypi-release-macos-x86-drop-windows
Jun 8, 2026
Merged

ci: make musl toolchain/zlib downloads resilient to musl.cc outages#148
rahlk merged 1 commit into
146-package-codeanalyzer-java-as-a-pypi-distribution-with-pypi-releaseymlfrom
fix/pypi-release-macos-x86-drop-windows

Conversation

@rahlk

@rahlk rahlk commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Follow-up to #147 (which merged before this commit landed).

Why

The musllinux-x86_64 / musllinux-aarch64 legs of the first release run failed at Set up musl toolchain:

curl: (7) Failed to connect to musl.cc port 443: Connection timed out

musl.cc is chronically unreliable.

What

setup-musl.sh now downloads via a fetch() helper that tries mirrors in order with curl --retry:

  • musl toolchain: musl-cc/musl.cc GitHub release (reliable from CI) → musl.cc. The mirror is byte-for-byte the same -native.tgz layout, so --strip-components=1, the CC name, and PATH are unchanged.
  • zlib: madler/zlib GitHub release → zlib.netzlib.net/fossils.

Avoids --retry-all-errors on purpose: the manylinux_2_28 container ships curl 7.61, which predates that flag.

These legs remain experimental: true / continue-on-error — a flaky upstream shouldn't block a PyPI release.

🤖 Generated with Claude Code

The musllinux legs failed with 'Failed to connect to musl.cc port 443:
Connection timed out'. musl.cc is chronically flaky. Download the musl
toolchain from a GitHub-hosted mirror (musl-cc/musl.cc) first, falling
back to musl.cc; do the same for zlib (madler/zlib release, then
zlib.net, then zlib.net/fossils). Add curl --retry with a connect
timeout. Avoids --retry-all-errors since the manylinux_2_28 container's
curl 7.61 predates it.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@rahlk rahlk merged commit c298f5f into 146-package-codeanalyzer-java-as-a-pypi-distribution-with-pypi-releaseyml Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant