-
Notifications
You must be signed in to change notification settings - Fork 13k
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.
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
Only produce .xz tarballs on CI #80435
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me with nit fixed
.as_ref() | ||
.and_then(|formats| formats.get(0)) | ||
.map(|s| s.as_str()) | ||
.unwrap_or("gz"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm, I think we should probably panic if the list is defined but empty, that seems like someone is doing the wrong thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added an assert to ensure the list is not empty.
The option allows to add or remove compression formats used while producing dist tarballs.
78fe658
to
d0d0ee0
Compare
@bors r=Mark-Simulacrum |
📌 Commit d0d0ee0 has been approved by |
…=Mark-Simulacrum Only produce .xz tarballs on CI This PR adds a `./configure` option to choose which tarball compression formats to produce, and changes our CI configuration to only produce `.xz` tarballs. The release process will then recompress everything into `.gz` when producing a release. This will drastically reduce our storage costs for CI artifacts, as we'd stop storing the same data twice. **Stable, beta and nightly releases will not be affected by this at all.** Before landing this we'll need to increase the VM size of our release process, to recompress everything in a reasonable amount of time. r? `@Mark-Simulacrum`
This failed in #80496: https://github.com/rust-lang-ci/rust/runs/1624327931
@bors r- |
@bors r=Mark-Simulacrum rollup=never |
📌 Commit f6b8572d1cdad991d030d5b07492d7410a749293 has been approved by |
The job Click to see the possible cause of the failure (guessed by this bot)
|
f6b8572
to
5526d90
Compare
@bors r=Mark-Simulacrum rollup=never |
📌 Commit 5526d90 has been approved by |
⌛ Testing commit 5526d90 with merge 32f233eb3ad76bda1e72b3d92cfe57e8e0068cde... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry - submodule download failed |
☀️ Test successful - checks-actions |
Give a better error for download-ci-llvm if .xz is not supported Previously: ``` curl: (22) The requested URL returned error: 404 failed to run: curl -# -y 30 -Y 10 --connect-timeout 30 --retry 3 -Sf -o /tmp/tmp6ptXJV https://ci-artifacts.rust-lang.org/rustc-builds/99ad5a1a2824fea1ecf60068fd3636beae7ea2da/rust-dev-nightly-x86_64-unknown-linux-gnu.tar.gz ``` Now: ``` error: XZ support is required to download LLVM help: consider disabling `download-ci-llvm` or using a different version of python Build completed unsuccessfully in 0:00:00 ``` Follow-up to rust-lang#80435. r? `@Mark-Simulacrum`
This PR adds a
./configure
option to choose which tarball compression formats to produce, and changes our CI configuration to only produce.xz
tarballs. The release process will then recompress everything into.gz
when producing a release.This will drastically reduce our storage costs for CI artifacts, as we'd stop storing the same data twice. Stable, beta and nightly releases will not be affected by this at all.
Before landing this we'll need to increase the VM size of our release process, to recompress everything in a reasonable amount of time.
r? @Mark-Simulacrum