-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Rollup of 12 pull requests #145003
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 12 pull requests #145003
Conversation
Co-authored-by: Tshepang Mbambo <hopsi@tuta.io>
Currently the Args new function is scope constrained to pub(super) but this stops me from being able to construct Args structs in unit tests.
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
The current `rust-version = "1.63"` was inherited from rayon, but it doesn't make sense to limit this in the compiler workspace. Having any setting at all has effects on tools like `cargo info` that try to infer the MSRV when the workspace itself doesn't specify it. Since we are the compiler, our only MSRV is whatever bootstrapping requires.
libs-api has agreed to rename these functions to `isolate_highest_one`/`isolate_lowest_one`
This fixes a few intrinsic docs that had a link directly to itself instead of to the correct function in the `mem` module.
This makes it possible to bless the snapshot files used by `diff()` in newly-created run-make tests, without having to create the files manually beforehand.
…=jieyouxu Rehome 33 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` rust-lang#143902 divided into smaller, easier to review chunks. Part of rust-lang#133895 Methodology: 1. Refer to the previously written `tests/ui/SUMMARY.md` 2. Find an appropriate category for the test, using the original issue thread and the test contents. 3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers) 4. Rename the tests to make their purpose clearer Inspired by the methodology that ``@Kivooeo`` was using. r? ``@jieyouxu``
…oxyUwU Add documentation for unstable_feature_bound There is more detail and explanation in https://hackmd.io/``````@tiif/Byd3mq7Ige`````` Original PR that implemented this: rust-lang#140399 r? ``````@BoxyUwU`````` to nominate for types team discussion
Change visibility of Args new function Currently the Args new function is constrained to pub(super) but this stops me from being able to construct Args structs in unit tests. This pull request is to change this to pub.
… r=fee1-dead Add regression tests for seemingly fixed issues Closes rust-lang#104314 Closes rust-lang#125866
…=fmease [rustdoc] Fix wrong `i` tooltip icon Current wrong display: <img width="334" height="37" alt="Screenshot From 2025-08-04 17-42-38" src="https://github.com/user-attachments/assets/57046475-6162-487f-998f-ebb2434c111d" /> With the fix: <img width="334" height="37" alt="image" src="https://github.com/user-attachments/assets/e761a103-dc39-4e30-8c8e-cfc7fab52fde" /> r? ``@fmease``
…ctives-hint, r=clubby789 compiletest: add hint for when a ui test produces no errors
…iper Correct the use of `must_use` on btree::IterMut I'm working on stricter target checking for attributes and found this one
Drop `rust-version` from `rustc_thread_pool` The current `rust-version = "1.63"` was inherited from rayon, but it doesn't make sense to limit this in the compiler workspace. Having any setting at all has effects on tools like `cargo info` that try to infer the MSRV when the workspace itself doesn't specify it. Since we are the compiler, our only MSRV is whatever bootstrapping requires.
…eLapkin Autolabel PRs that change explicit tail call tests as `F-explicit_tail_calls` mrrrow~
run-make: Allow blessing snapshot files that don't exist yet This makes it possible to bless the snapshot files used by `diff()` in newly-created run-make tests, without having to create the files manually beforehand. r? jieyouxu
…htriplett num: Rename `isolate_most_least_significant_one` functions Tracking issue - rust-lang#136909 libs-api has agreed to rename these unstable functions to `isolate_highest_one`/`isolate_lowest_one` rust-lang#136909 (comment) `isolate_most_significant_one` -> `isolate_highest_one` `isolate_least_significant_one` -> `isolate_lowest_one`
Fix some doc links for intrinsics This fixes a few intrinsic docs that had a link directly to itself instead of to the correct function in the `mem` module.
@bors r+ rollup=never p=5 |
Since we potentially have time before it hits the top of the queue, I'd like to check this which has bitten several of us recently with an unknown origin, on rollup which included some PR on this list: @bors2 try jobs=test-various |
Rollup of 12 pull requests try-job: test-various
Also watch out for #144995 (comment), which gives so little information that I have not been able to attribute it to any particular PR. |
Yes, I had tried to find out what went wrong too and failed. |
☀️ 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 8fb40f7 (parent) -> 29cdc6a (this PR) Test differencesShow 284 test diffsStage 1
Stage 2
(and 86 additional test diffs) Additionally, 98 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 29cdc6a109ee98a382f974bf89d3971b4385399c --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 |
📌 Perf builds for each rolled up PR:
previous master: 8fb40f798a In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (29cdc6a): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 6.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.6%)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: 464.179s -> 464.98s (0.17%) |
Successful merges:
tests/ui/issues/
tests to other subdirectories undertests/ui/
#144552 (Rehome 33tests/ui/issues/
tests to other subdirectories undertests/ui/
)i
tooltip icon #144913 ([rustdoc] Fix wrongi
tooltip icon)must_use
on btree::IterMut #144926 (Correct the use ofmust_use
on btree::IterMut)rust-version
fromrustc_thread_pool
#144928 (Droprust-version
fromrustc_thread_pool
)F-explicit_tail_calls
#144945 (Autolabel PRs that change explicit tail call tests asF-explicit_tail_calls
)isolate_most_least_significant_one
functions #144971 (num: Renameisolate_most_least_significant_one
functions)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup