-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Rollup of 14 pull requests #144269
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 14 pull requests #144269
Conversation
Mistake in section serialization in rustc
…sion See RUST-143834.
From `#[align]` -> `#[rustc_align]`. Attributes starting with `rustc` are always perma-unstable and feature-gated by `feature(rustc_attrs)`. See regression RUST-143834. For the underlying problem where even introducing new feature-gated unstable built-in attributes can break user code such as ```rs macro_rules! align { () => { /* .. */ }; } pub(crate) use align; // `use` here becomes ambiguous ``` refer to RUST-134963. Since the `#[align]` attribute is still feature-gated by `feature(fn_align)`, we can rename it as a mitigation. Note that `#[rustc_align]` will obviously mean that current unstable user code using `feature(fn_aling)` will need additionally `feature(rustc_attrs)`, but this is a short-term mitigation to buy time, and is expected to be changed to a better name with less collision potential. See <https://rust-lang.zulipchat.com/#narrow/channel/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202025-07-17/near/529290371> where mitigation options were considered.
…ost) code generation
minor: remove unused var
It used to search for `'foo` which won't find `'r#foo`, now we search for `foo` instead.
Subtree update of `rust-analyzer` r? ```@ghost```
Don't use another main test file as auxiliary In this case, the exact extern crate isn't very important, it just needs to not be another main test file. This is part of the changes needed to address the spurious failures from a main test `../removing-extern-crate.rs` being both an auxiliary and a main test file, causing fs races due to multiple `rustc` processes in multiple test threads trying to build the main test file both as a main test and also as an auxiliary at around the same time. Part 1 of rust-lang#144237. r? ``@RalfJung`` (or compiler)
rustc-dev-guide subtree update Subtree update of `rustc-dev-guide` to rust-lang/rustc-dev-guide@cca2337. Created using https://github.com/rust-lang/josh-sync. r? ```@ghost```
…obzol opt-dist: make `artifact-dir` an absolute path for `opt-dist local` ...like for CI environments. the same logic applied as for `build_dir`. fixes the issue where some intermediate steps fail due to path being relative to an active directory r? Kobzol try-job: dist-x86_64-msvc try-job: dist-x86_64-linux
@bors r+ rollup=never p=5 |
☀️ 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 3f9f20f (parent) -> 9748d87 (this PR) Test differencesShow 2052 test diffsStage 1
Stage 2
(and 34 additional test diffs) Additionally, 1918 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 9748d87dc70a9a6725c5dbd76ce29d04752b4f90 --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: 3f9f20f71d In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (9748d87): 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)Results (secondary 1.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 2.2%)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: 465.766s -> 465.536s (-0.05%) |
Successful merges:
check
for compiletest and RA using tool macro #143816 (Implementcheck
for compiletest and RA using tool macro)#[align]
name resolution ambiguity regression with a rename #144080 (Mitigate#[align]
name resolution ambiguity regression with a rename)rust-analyzer
#144243 (Subtree update ofrust-analyzer
)artifact-dir
an absolute path foropt-dist local
#144254 (opt-dist: makeartifact-dir
an absolute path foropt-dist local
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup