Skip to content

Add bootstrap step to test compiler-builtins - #164162

Open
Kobzol wants to merge 4 commits into
rust-lang:mainfrom
Kobzol:test-builtins
Open

Kobzol wants to merge 4 commits into
rust-lang:mainfrom
Kobzol:test-builtins

Conversation

@Kobzol

@Kobzol Kobzol commented Oct 11, 2026 •

Copy link
Copy Markdown
Member

View all comments

This is a revival of #142106.

r? @tgross35

@rustbot

rustbot commented Oct 11, 2026

Copy link
Copy Markdown
Collaborator

compiler-builtins is developed in its own repository. If possible, consider making this change to rust-lang/compiler-builtins instead.

cc @tgross35

@rustbot rustbot added A-compiler-builtins Area: compiler-builtins (https://github.com/rust-lang/compiler-builtins) A-testsuite Area: The testsuite used to check the correctness of rustc 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-libs Relevant to the library team, which will review and decide on the PR/issue. labels Oct 11, 2026
@rustbot

rustbot commented Oct 11, 2026

Copy link
Copy Markdown
Collaborator

tgross35 is currently at their maximum review capacity.
They may take a while to respond.


builder.ensure(compile::Std::new(compiler, target));

const COMPILER_BUILTINS_ALLOW_FEATURES: &[&str] = &[

@Kobzol Kobzol Oct 11, 2026 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This list is only needed because we use Mode::ToolStd. This mode checks that the tool isn't using unstable features by default, which is a bit strange, because tools using the local standard library are usually quite special. That being said, we do have things like build-manifest, which should actually be stable.

So I didn't change this step to use another mode, but rather opted into just enumerating all the used unstable features here, same as we do e.g. for test-float-parse.

View changes since the review

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@tgross35 tgross35 left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for finishing this up! I don't know what I got stuck on at #142106, this seems pretty close.

The feature gate changes were done in the subtree already, so I started a sync at #164333. r=me once rebased after that merges.

@SnoozeThis #164333

View changes since this review

@Kobzol

Kobzol commented Oct 16, 2026

Copy link
Copy Markdown
Member Author

@bors r=tgross35 rollup=never note="Hard to tell if the tests work everywhere"

Thanks, let's try!

@rust-bors

rust-bors Bot commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 15cecde has been approved by tgross35

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 16, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Oct 16, 2026
Add bootstrap step to test compiler-builtins

This is a revival of #142106.

r? @tgross35
@rust-log-analyzer

This comment has been minimized.

@rust-bors rust-bors Bot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Oct 16, 2026
@rust-bors

rust-bors Bot commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

💔 Test for b3fa158 failed: CI. Failed job:

@tgross35

Copy link
Copy Markdown
Member

I'm not sure where that's coming from, why isn't it just using the version in

version = "1.4.3"
? I guess and
cc = { version = "1.2", optional = true }
could be bumped if it helps.

@tgross35

Copy link
Copy Markdown
Member

I suppose,
@rustbot author

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 18, 2026
@Kobzol

Kobzol commented Oct 20, 2026

Copy link
Copy Markdown
Member Author

@bors try jobs=test-x86_64-gnu-distcheck

rust-bors Bot pushed a commit that referenced this pull request Oct 20, 2026
Add bootstrap step to test compiler-builtins


try-job: test-x86_64-gnu-distcheck
@Kobzol

Kobzol commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

Huh, turns out that I should have rebased this PR before picking it up 😆 I was using a quite old stdlib lockfile.

@rustbot

rustbot commented Oct 26, 2026

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@Kobzol

Kobzol commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

@bors try jobs=test-x86_64-gnu-distcheck

@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Oct 26, 2026
Add bootstrap step to test compiler-builtins


try-job: test-x86_64-gnu-distcheck
@rust-bors

rust-bors Bot commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 61cadb7 failed: CI. Failed job:

@rust-log-analyzer

This comment has been minimized.

@Kobzol

Kobzol commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

I was on the wrong track. The problem is this.

@bors try jobs=test-x86_64-gnu-distcheck

@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Oct 26, 2026
Add bootstrap step to test compiler-builtins


try-job: test-x86_64-gnu-distcheck
@rust-bors

rust-bors Bot commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: d357e84 (d357e844d819c9f9ffce588d6662d3c84e36bd58)
Base parent: aaf324d (aaf324d50a7dcb17aae7f2a37e15ff143d980c6e)

@Kobzol

Kobzol commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

Yay, finally! Let's try again.

@bors r=tgross35

@rust-bors

rust-bors Bot commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 8f496d4 has been approved by tgross35

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Oct 26, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Oct 26, 2026
Add bootstrap step to test compiler-builtins



This is a revival of #142106.

r? @tgross35
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-x86_64-gnu-distcheck failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
failures:

---- tempfile::tests::named_temp_file_new_creates_file stdout ----

thread 'tempfile::tests::named_temp_file_new_creates_file' (395576) panicked at src/tools/rust-analyzer/crates/stdx/src/tempfile.rs:238:9:
assertion failed: !fs::exists(path).unwrap()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---- tempfile::tests::named_temp_file_new_creates_file stdout end ----

failures:
    tempfile::tests::named_temp_file_new_creates_file

test result: FAILED. 7 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.29ms

error: test failed, to rerun pass `-p stdx --lib`
Build completed unsuccessfully in 1:18:50
make: *** [Makefile:49: check] Error 1
Bootstrap failed while executing `test distcheck`
Currently active steps:
test::Distcheck {  } at src/bootstrap/src/core/build_steps/test.rs:4084
Command `make check [workdir=/tmp/distcheck/distcheck-rustc-src]` failed with exit code 2
Created at: src/bootstrap/src/core/build_steps/test.rs:4132:5
Executed at: src/bootstrap/src/core/build_steps/test.rs:4138:10

Command has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 1:27:11
  local time: Mon Oct 26 16:59:35 UTC 2026
  network time: Mon, 26 Oct 2026 16:59:35 GMT
##[error]Process completed with exit code 1.
##[group]Run echo "disk usage:"

@rust-bors rust-bors Bot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Oct 26, 2026
@rust-bors

rust-bors Bot commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 5e245fa failed: CI. Failed job:

@tgross35

Copy link
Copy Markdown
Member

I think that's been a spurious failure

@bors retry

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 26, 2026
@Kobzol

Kobzol commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

It looks like so, yeah. Funny that it happened in distcheck again..

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-compiler-builtins Area: compiler-builtins (https://github.com/rust-lang/compiler-builtins) A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) 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.

5 participants