-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Rollup of 4 pull requests #95999
Rollup of 4 pull requests #95999
Conversation
…rk-Simulacrum Always use system `python3` on MacOS This PR includes 2 changes: 1. Always use the system Python found at `/usr/bin/python3` on MacOS 2. Removes the hard requirement on having `python` in your system path if you didn't specify alternatives. The proposed change will instead attempt to find and use in order: `python` -> `python3` -> `python2`. This change isn't strictly necessary but without any change to this check, the original issue inspiring this change will still exist. Fixes rust-lang#95204 r? ```@jyn514```
…s-screenshot-link, r=Dylan-DPC Fix broken link in coverage tools docs During stabilization the link to example screenshot wad not updated, making rendered docs somewhat less useful. Move that screenshot from unstable book into rustc docs and make documentation point to that new place. Also remove `/img` in unstable book since there are no more any files there.
Fix spelling in docs for `can_not_overflow` Introduced in rust-lang#95399
…compiler-errors diagnostics: regression test for spurrious "help: store this in the heap" Closes rust-lang#82446
@bors r+ rollup=never p=5 |
📌 Commit 2b4c4df has been approved by |
⌛ Testing commit 2b4c4df with merge 51c5e14ef798ec6488a0b64d6af832e73fdb0a00... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (b768f24): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
Visiting for weekly performance triage. This had no primary regressions; for secondary, it caused a 1.2% regression on externs incr-full, in debug and opt variants. It also caused a 0.5% regression on tt-muncher (opt full). I don't see any reason why the PRs in this rollup would have anything to do with that regression. @rustbot label +perf-regression-triaged |
Successful merges:
python3
on MacOS #95441 (Always use systempython3
on MacOS)can_not_overflow
#95984 (Fix spelling in docs forcan_not_overflow
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup