Rollup of 5 pull requests - #160974
Conversation
Also includes `HELP` checks for add-tuple-within-arguments.rs to make it clear that the referenced rules are being tested
Was already stable when using explicit types (e.g. `Vec<u8>`). `WriteThroughCursor` is still unstable/hidden.
…tt,Urgau Ensure that restriction paths are ancestors fix: rust-lang#160873 This PR moves the check that `impl` and `mut` restriction paths resolve to ancestor modules from `rustc_resolve` to `rustc_ast_lowering`. This ensures that `RestrictionKind::Restricted` in HIR always refers to an ancestor module. If a restriction path resolves to a non-ancestor, we emit an error and recover by lowering the restriction as `RestrictionKind::Unrestricted`. Tracking Issue: rust-lang#105077 r? @Urgau cc @jhpratt
…ple, r=traviscross tests/ui/tuple: add annotations for reference rules Also includes `HELP` checks for add-tuple-within-arguments.rs to make it clear that the referenced rules are being tested
Disable some tests for ohos target I ran into some test failures when trying to run the full test suite for ohos target. There're a few more but I'm not certain of those yet.
…bility_fix, r=clarfonthey Fix improper stability of `Write for Cursor<W: WriteThroughCursor>` Was already stable when using explicit types (e.g. `Vec<u8>`). `WriteThroughCursor` is still unstable/hidden. Tracking Issue: rust-lang#154046 Zulip Discussion: [#general > ✔ CI Failure With and Without Stability Attribute](https://rust-lang.zulipchat.com/#narrow/channel/122651-general/topic/.E2.9C.94.20CI.20Failure.20With.20and.20Without.20Stability.20Attribute/with/615974133) # Description Fixes an oversight in how the `Write for Cursor<W: WriteThroughCursor>` implementation was written. While `core::io` was unstable, a stability attribute for this implementation was not required. However, once that module is marked as stable (even when `Cursor` and `Write` are not publicly stably exported), a stability attribute is required. Since `Write` and `Cursor` are both stable items (just not stable to access via `core::io`), the implementation must be marked as stable. While it is possible to use [#[unstable_feature_bound(core_io)]](https://rustc-dev-guide.rust-lang.org/stability.html#unstable_feature_bound) to allow that implementation to be unstable, we do need users to have access to it stably, since it is how implementations such as `Write for Cursor<Vec<u8>>` are accessed. This is also why this implementation is marked as stable since `1.0.0`, since that is the earliest downstream implementation we must permit. --- ## Notes - No AI tooling of any kind was used during the creation of this PR.
Fix handling of relative paths starting with a dot in bootstrap We missed this in rust-lang#160855. Fixes: rust-lang#160968 CC @Zalathar r? jieyouxu
This comment has been minimized.
This comment has been minimized.
Rollup of 5 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 41fb9d4587 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
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 41fb9d4 (parent) -> ab8058a (this PR) Test differencesShow 18 test diffsStage 0
Stage 1
Stage 2
Additionally, 14 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 ab8058aa09e8c14b86b3d06c08ade66f863d22fe --output-dir test-dashboardAnd 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 (ab8058a): comparison URL. Overall result: ❌ regressions - 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 -2.6%, secondary -0.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 0.4%, secondary -0.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 455.63s -> 478.868s (5.10%) |
Successful merges:
Write for Cursor<W: WriteThroughCursor>#160952 (Fix improper stability ofWrite for Cursor<W: WriteThroughCursor>)r? @ghost
Create a similar rollup