-
-
Notifications
You must be signed in to change notification settings - Fork 15.9k
Passing --no-doc to ./x.py test causes panic_abort tests to fail #80124
Copy link
Copy link
Open
Labels
A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Description
Activity
Metadata
Metadata
Assignees
Labels
A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Running
./x.py test --stage 1 --no-docon the latest version of nightly (#80114) causes the test suite to crash with the following error:This seems like a bug in the bootstrapper where
--no-doccauses tests to be erroneously compiled with the abort panic strategy, since tests pass as expected with./x.py test --stage 1(--no-docomitted)This error can be also triggered with a subset of the test suite by running
./x.py test library/panic_abort --stage 1 --no-doc