Skip to content
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

Support loading version information from xz tarballs #110436

Merged
merged 1 commit into from
May 3, 2023

Conversation

Mark-Simulacrum
Copy link
Member

This is intended to allow us to move recompression from xz (produced in CI) to gz after an initial manifest run, which produces a list of actually required artifacts. The rest are then deleted, which means that we can avoid recompressing them, saving a bunch of time.

This is essentially untested and more might be needed, will run a patched promote-release against try artifacts from this PR. If we do go ahead with this we'll either need to backport this patch to beta/stable, wait for it to propagate, or temporarily recompress to gzip but not xz tarballs (or similar).

r? @pietroalbini

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 17, 2023
@rustbot

This comment was marked as resolved.

Mark-Simulacrum added a commit to Mark-Simulacrum/promote-release that referenced this pull request Apr 17, 2023
This allows build-manifest to run successfully; upstream patch
rust-lang/rust#110436 to make this fully
unnecessary is pending review and release across all channels.
Mark-Simulacrum added a commit to Mark-Simulacrum/promote-release that referenced this pull request Apr 17, 2023
This allows build-manifest to run successfully; upstream patch
rust-lang/rust#110436 to make this fully
unnecessary is pending review and release across all channels.
@pietroalbini
Copy link
Member

@bors r+ rollup

Rolling up as this code is not executed by CI.

@bors
Copy link
Contributor

bors commented May 2, 2023

📌 Commit e40a446 has been approved by pietroalbini

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 2, 2023
bors added a commit to rust-lang-ci/rust that referenced this pull request May 3, 2023
Rollup of 11 pull requests

Successful merges:

 - rust-lang#107978 (Correctly convert an NT path to a Win32 path in `read_link`)
 - rust-lang#110436 (Support loading version information from xz tarballs)
 - rust-lang#110791 (Implement negative bounds for internal testing purposes)
 - rust-lang#110874 (Adjust obligation cause code for `find_and_report_unsatisfied_index_impl`)
 - rust-lang#110908 (resolve: One more attempt to simplify `module_children`)
 - rust-lang#110943 (interpret: fail more gracefully on uninit unsized locals)
 - rust-lang#111062 (Don't bail out early when checking invalid `repr` attr)
 - rust-lang#111069 (remove pointless `FIXME` in `bootstrap::download`)
 - rust-lang#111086 (Remove `MemEncoder`)
 - rust-lang#111097 (Avoid ICEing miri on layout query cycles)
 - rust-lang#111112 (Add some triagebot notifications for nnethercote.)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 32f3ddb into rust-lang:master May 3, 2023
@rustbot rustbot added this to the 1.71.0 milestone May 3, 2023
@Mark-Simulacrum Mark-Simulacrum deleted the support-xz-version branch May 6, 2023 23:28
Mark-Simulacrum added a commit to rust-lang/promote-release that referenced this pull request May 7, 2023
This allows build-manifest to run successfully; upstream patch
rust-lang/rust#110436 to make this fully
unnecessary is pending review and release across all channels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants