Rollup of 23 pull requests#157828
Conversation
Update the target spec & relevant documentation for aarch64-unknown-freebsd to reflect it being promoted to Tier 2. Implements MCP: rust-lang/compiler-team#961 Signed-off-by: Kajetan Puchalski <kajetan.puchalski@arm.com>
This updates the rust-version file to 4f84d9f.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@4f84d9f Filtered ref: rust-lang/miri@4889255 Upstream diff: rust-lang/rust@bef8e62...4f84d9f This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
`-Zremap-cwd-prefix=<to>` was applied inside `parse_remap_path_prefix`, which resolved `std::env::current_dir()` and pushed `(cwd, to)` onto `remap_path_prefix`. That option is `[TRACKED_NO_CRATE_HASH]`, so the absolute working directory entered the incremental command-line-args hash, and building the same sources from a different directory (e.g. a Bazel sandbox, whose path contains a per-action counter) purged the whole incremental cache even though the remapped output is identical. `--remap-path-prefix` and `-Zremap-cwd-prefix` already have separate options (`remap_path_prefix` and `remap_cwd_prefix`). Keep each option holding exactly its own flag, and apply `-Zremap-cwd-prefix` in `file_path_mapping` -- i.e. when building the (untracked) applied `FilePathMapping` -- rather than when parsing/tracking options. The absolute cwd then lives only in the runtime mapping, never in a tracked field. Output is unchanged (the cwd entry is still appended last). Tracking stays sound: the cwd's effect is tracked via `remap_cwd_prefix` (the target prefix baked into output) and `working_dir` (whose `RealFileName` hash includes the real path only when it was not fully remapped, i.e. exactly when the cwd can leak into output). The stable `--remap-path-prefix` flag is unchanged in data and in tracking. A unit test guards against the cwd being merged back into `remap_path_prefix`.
This updates the rust-version file to 76dfce2.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@76dfce2 Filtered ref: rust-lang/miri@d3a4cd9 Upstream diff: rust-lang/rust@4f84d9f...76dfce2 This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
CreateFileW: retry to deal with race conditions
This is virtually the same target as the existing -gnu target, but using the ELFv2 ABI instead of the ELFv1 ABI and made possible now that we expose target_abi = "elfv1" or "elfv2" on the 64-bit PowerPC targets.
This updates the rust-version file to 3179a47.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@3179a47 Filtered ref: rust-lang/miri@b296633 Upstream diff: rust-lang/rust@76dfce2...3179a47 This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
bump 'aes'
This comment has been minimized.
This comment has been minimized.
Rollup of 23 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 try-job: x86_64-mingw-1 try-job: i686-msvc-2
|
@bors treeopen |
|
Tree is now open for merging. |
This comment has been minimized.
This comment has been minimized.
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 3bdd7f8 (parent) -> 6540795 (this PR) Test differencesShow 657 test diffsStage 0
Stage 1
Stage 2
Additionally, 578 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 65407954098ca3c19f0d46092cb374b5d3e9dc3c --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 |
|
📌 Perf builds for each rolled up PR:
previous master: 3bdd7f86fc In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (6540795): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary -0.4%, secondary 1.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis perf run didn't have relevant results for this metric. Binary sizeResults (primary 0.0%, secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 519.494s -> 518.069s (-0.27%) |
Successful merges:
-Zremap-cwd-prefixin incremental compilation #157348 (Don't track cwd for-Zremap-cwd-prefixin incremental compilation)#[pin_v2]for explicit pin-projection patterns #157680 (Require#[pin_v2]for explicit pin-projection patterns)aarch64-apple-macos-26for evaluatingmacos-26runner images #157688 (Create experimental test jobaarch64-apple-macos-26for evaluatingmacos-26runner images)&raw EXPRas a missing comma #157079 (Don't recover&raw EXPRas a missing comma)TypeFoldable_Generic#157695 (Extend capabilities ofTypeFoldable_Generic)errors.rsfile todiagnostics.rs(7/N) #157803 (Renameerrors.rsfile todiagnostics.rs(7/N))Failed merges:
errors.rsfile todiagnostics.rs(6/N) #157752 (Renameerrors.rsfile todiagnostics.rs(6/N))r? @ghost
Create a similar rollup