-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Tracking issue for only producing .xz on CI #80753
Comments
Forgot to create the tracking issue when the work started :) |
I've got an inventory of the rust-lang-ci2 bucket. Observations:
|
I think this is done. I will check the next inventory and, if so, revert rust-lang/simpleinfra@16e3aaa. For the record, here's my dirty script:
|
Correction - I deleted the nightly ones, so >500k combined. This looks like it's reduced our storage of ci2 from 78.5TiB to ~55TiB. There are still a few other .gz files:
The first set are .gz files that mention nightly - not sure where they've come from, maybe they got missed in the initial run? |
What's the status of this? I think at this point we've stopped uploading new .gz files? |
This is done. |
This issue tracks the work needed to only produce .xz tarballs on CI, recompressing them into .gz only during the release process. The effort will greatly reduce the amount of artifacts we need to store.
Implementation work needed:
rust-installer
to allow choosing which tarballs to produce Allow specifying the wanted compression formats at runtime rust-installer#105.gz
tarballs from the artifacts bucketBugs caused by this:
./x.py install
crashed due to a different directory structure x.py install fails when run outside of Rust source directory #80494 Fix broken ./x.py install #80514The text was updated successfully, but these errors were encountered: