Skip to content

Conversation

@Zalathar
Copy link
Member

Investigating the long duration of x86_64-gnu-aux observed in #150900 (comment) and subsequent PRs.

r? ghost

@rustbot
Copy link
Collaborator

rustbot commented Jan 10, 2026

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

Some changes occurred in compiler/rustc_passes/src/check_attr.rs

cc @jdonszelmann

Some changes occurred in compiler/rustc_hir/src/attrs

cc @jdonszelmann

@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-tidy Area: The tidy tool S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Jan 10, 2026
@rustbot
Copy link
Collaborator

rustbot commented Jan 10, 2026

⚠️ Warning ⚠️

  • There are issue links (such as #123) in the commit messages of the following commits.
    Please move them to the PR description, to avoid spamming the issues with references to the commit, and so this bot can automatically canonicalize them to avoid issues with subtree.

@Zalathar
Copy link
Member Author

@rustbot experimental

@Zalathar Zalathar added S-experimental Status: Ongoing experiment that does not require reviewing and won't be merged in its current state. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 10, 2026
@Zalathar
Copy link
Member Author

@bors try jobs=x86_64-gnu-aux

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Jan 10, 2026
[EXPERIMENT] Revert things to investigate long job times

try-job: x86_64-gnu-aux
@Zalathar
Copy link
Member Author

From looking at the actual changes, my guess is that #149318 has exploded the time taken to run library/alloctests under MIRI.

@Zalathar
Copy link
Member Author

From looking at the actual changes, my guess is that #149318 has exploded the time taken to run library/alloctests under MIRI.

Looking at timestamps in the build log confirms that the random_patterns alloctest is taking 1.5 hours to run under Miri.

I have a proposed fix at #150947.

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 11, 2026

☀️ Try build successful (CI)
Build commit: e5162c9 (e5162c94dbec384521b8ef45281239cf80e0b3af, parent: f57eac1bf98cb5d578e3364b64365ec398c137df)

@Zalathar Zalathar closed this Jan 11, 2026
@Zalathar Zalathar deleted the revert branch January 11, 2026 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-tidy Area: The tidy tool S-experimental Status: Ongoing experiment that does not require reviewing and won't be merged in its current state. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants