-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Make it possible to x install
Cranelift and LLVM bitcode linker
#146927
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
Conversation
7de19e1
to
ffca2f0
Compare
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.
@bors r+ rollup |
Make it possible to `x install` Cranelift and LLVM bitcode linker It was not possible to install these before, as they were not in the install step description list. Fixes: rust-lang#140331 r? `@jieyouxu`
Rollup of 8 pull requests Successful merges: - #146818 (constify {float}::total_cmp()) - #146896 (rustc-dev-guide subtree update) - #146898 (Update books) - #146899 (Fix a crash/mislex when more than one frontmatter closing possibility is considered) - #146904 (#140368 Mutex/RwLock/ReentrantLock::data_ptr to be const fn) - #146907 (add regression test for issue 146537) - #146927 (Make it possible to `x install` Cranelift and LLVM bitcode linker) - #146931 (miri subtree update) r? `@ghost` `@rustbot` modify labels: rollup
@bors try jobs=i686-gnu-2 |
This comment has been minimized.
This comment has been minimized.
Make it possible to `x install` Cranelift and LLVM bitcode linker try-job: i686-gnu-2
@bors r=jieyouxu rollup=never Let's try again. |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing c0ee51f (parent) -> 4082d6a (this PR) Test differencesShow 4 test diffs4 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 4082d6a3f0347c2fc4b8c8d5a6a38ed7248fa161 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (4082d6a): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 471.818s -> 470.544s (-0.27%) |
It was not possible to install these before, as they were not in the install step description list.
Fixes: #140331
r? @jieyouxu