[beta] backports - #160714
Conversation
(cherry picked from commit facc787)
(cherry picked from commit cb797b8)
fastmod --fixed-strings '#[splat]' '#[rustc_splat]'
fastmod --fixed-strings '`splat` attribute' '`rustc_splat` attribute'
fastmod --fixed-strings '$splat$' '$rustc_splat$'
fastmod 'v0(.*)#\[rustc_splat\]' 'v0${1}#[splat]' tests/ui/splat/splat-mangling.rs
(cherry picked from commit e574edf)
This comment has been minimized.
This comment has been minimized.
(cherry picked from commit bc1bb27)
Mitigation for [RUST-159429]. The recurring problem is that built-in attributes are treated differently compared to ordinary prelude attributes, built-in attributes, even while unstable, can name-collide with stable macro re-exports of the same name (and proc-macro helper attributes of the same name), which can break stable code. See [RUST-134964]. [RUST-159429]: rust-lang#159429 [RUST-134963]: rust-lang#134963 (cherry picked from commit 0a0f6df)
(cherry picked from commit 44d291e)
To account for the renamed `#[rustc_unroll]` attribute. (cherry picked from commit 91ee1f3)
This stderr diff is a funny side-effect of renaming `#[unroll]` => `#[rustc_unroll]`, where the `#[rustc_unknown]` attribute name is just similar enough edit distance wise to `#[rustc_unroll]` that `#[rustc_unroll]` shows up as a plausible suggestion candidate, lol. (cherry picked from commit 945d2f3)
(cherry picked from commit d1265b7)
|
|
@bors r+ rollup=never p=1 |
This comment has been minimized.
This comment has been minimized.
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for 8ba9fdd failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for cda58a0 failed: CI. Failed job:
|
I'll mirror |
|
Why does the ncurses download give different SHA256 values each time? In https://triage.rust-lang.org/gha-logs/rust-lang/rust/93177803816, it's 7a98c4ac3ea276a8da4500556171b6dee8ad4f0d30b211f1b79c42a23f628006 In https://triage.rust-lang.org/gha-logs/rust-lang/rust/93013015396, it's 8c5780bef692c331729f257866b0dd1ed4681fc4b2b65993c4c9a5099b2e8054 |
|
CT-NG 1.28.0 Very strange. Checking GNU |
|
|
|
|
Let's try again... |
|
@bors try jobs=dist-powerpc64-linux-musl,dist-loongarch64-linux |
This comment has been minimized.
This comment has been minimized.
[beta] backports try-job: dist-powerpc64-linux-musl try-job: dist-loongarch64-linux
This comment has been minimized.
This comment has been minimized.
|
@bors r=cuviper rollup=never p=1 |
|
aarch64-apple is being slow but looks likely to still finish |
I wonder if it's not really hashing a tarball at all, but rather an HTTP error with headers (including timestamps). |
View all comments
cfg_select!rustfmt: Discover modules viacfg_select!#158372#[unroll]=>#[rustc_unroll]to mitigate nameres ambiguity Rename#[unroll]=>#[rustc_unroll]to mitigate nameres ambiguity #160211r? me