Skip to content

Followup on pruning unused files #23

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

Closed
pietroalbini opened this issue Oct 27, 2020 · 5 comments
Closed

Followup on pruning unused files #23

pietroalbini opened this issue Oct 27, 2020 · 5 comments
Labels
A-optimization Issue that affects the speed or resource usage of promote-release C-new-feature A new feature that we could implement

Comments

@pietroalbini
Copy link
Member

I tried doing a nightly release on dev-static with #21 (pruning unused files) enabled, and the feature is definitely not ready to be enabled in production. This issue tracks the work needed to make it production ready.

@pietroalbini
Copy link
Member Author

pietroalbini commented Oct 27, 2020

The difference between the files uploaded by the current code in production and the files uploaded by the experimental code on dev is in this gist. To summarize (:green_square: intentional -- :orange_square: intentional but surprising -- :red_square: bug to fix):

  • 🟩 The build-manifest component was removed.
  • 🟩 The rust-dev component was removed.
  • 🟩 The cpu-{builder}.csv files were removed.
  • 🟩 The image-{builder}.txt files were removed.
  • 🟩 The toolstates-{platform}.txt files were removed.
  • 🟧 The miri component was removed.
  • 🟧 The rust-docs component was removed on multiple targets.
    • Affected targets: aarch64-apple-darwin, aarch64-apple-ios, aarch64-pc-windows-msvc, x86_64-apple-ios, i586-pc-windows-msvc
    • These targets do not have docs enabled in the manifest, as they're not Tier 1.
  • 🟧 The i686-unknown-freebsd target was removed.
  • 🟥 The .pkg macOS installers were removed.
  • 🟥 The .msi Windows installers were removed.

@pietroalbini
Copy link
Member Author

pietroalbini commented Oct 27, 2020

Oh, wow, there is a reason why everything but rust-std for the i686-unknown-freebsd target was removed: we're running a full dist builder for it, but it's marked as target-only in build-manifest. We built full dist artifacts for it since literally forever, but we never made them usable through rustup 🤦

@pietroalbini
Copy link
Member Author

The missing .pkg and .msi will be fixed by rust-lang/rust#78486.

@pietroalbini pietroalbini added A-optimization Issue that affects the speed or resource usage of promote-release C-new-feature A new feature that we could implement labels Oct 28, 2020
@pietroalbini
Copy link
Member Author

Did another run with the latest changes merged in, and the difference between the files uploaded by the current code in production and the files uploaded by the experimental code on dev is in this gist.

To summarize (:green_square: intentional -- :orange_square: intentional but surprising -- :red_square: bug to fix):

  • 🟩 The build-manifest component was removed.
  • 🟩 The rust-dev component was removed.
  • 🟩 The cpu-{builder}.csv files were removed.
  • 🟩 The image-{builder}.txt files were removed.
  • 🟩 The toolstates-{platform}.txt files were removed.
  • 🟧 The miri component was removed.
  • 🟧 The rust-docs component was removed on multiple targets.
    • Affected targets: aarch64-apple-darwin, aarch64-apple-ios, aarch64-pc-windows-msvc, x86_64-apple-ios, i586-pc-windows-msvc
    • These targets do not have docs enabled in the manifest, as they're not Tier 1.
  • 🟧 The i686-unknown-freebsd target was removed.

@pietroalbini
Copy link
Member Author

The PR enabling this was just merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-optimization Issue that affects the speed or resource usage of promote-release C-new-feature A new feature that we could implement
Projects
None yet
Development

No branches or pull requests

1 participant