Skip to content
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

Various coretests improvements #137679

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

bjorn3
Copy link
Member

@bjorn3 bjorn3 commented Feb 26, 2025

The first commit is not yet strictly necessary as directly testing libcore works though useless work, but will be necessary once #136642 migrates the liballoc tests into a separate package. The second commit fixes #137478 and ensures that coretests actually gets tested on all CI job. The third commit fixes an error that didn't get caught because coretests doesn't run on the wasm32 CI job.

This overrides the test=false flag in Cargo.toml and it shouldn't be
necessary as --tests is already passed.
@rustbot
Copy link
Collaborator

rustbot commented Feb 26, 2025

r? @Kobzol

rustbot has assigned @Kobzol.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added 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 Feb 26, 2025
@bjorn3 bjorn3 force-pushed the coretests_improvements branch from fc146ad to a535d6d Compare February 26, 2025 15:08
It is reasonable to expect that ./x.py test core is enough to run tests
when you are working on core. In addition it seems like CI for wasm32 at
least doesn't run coretests currently, which this commit fixes.
@RalfJung
Copy link
Member

The second commit fixes #137478, fixes rust-lang/miri-test-libstd#88 and

I don't think it does; miri-test-libstd does not use x.py.

@bjorn3
Copy link
Member Author

bjorn3 commented Feb 26, 2025

Removed it from the PR description again.

@Kobzol
Copy link
Contributor

Kobzol commented Feb 26, 2025

The changes make sense, but I don't know much about how std/core tests are configured, so would appreciate another look.

@jieyouxu?

@jieyouxu
Copy link
Member

Sure, I'll also take a look.

@jieyouxu jieyouxu self-assigned this Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

./x test library/core stopped working
5 participants