Skip to content

Conversation

GuillaumeGomez
Copy link
Member

@GuillaumeGomez GuillaumeGomez commented Sep 19, 2025

Needed for #146414.

Currently we ignore them in the GCC backend and until this situation changes, it'll block #146414.

r? @Kobzol

@rustbot rustbot added A-compiletest Area: The compiletest test runner 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) labels Sep 19, 2025
@rustbot
Copy link
Collaborator

rustbot commented Sep 19, 2025

Some changes occurred in src/tools/compiletest

cc @jieyouxu

@rust-log-analyzer

This comment has been minimized.

@GuillaumeGomez
Copy link
Member Author

CI passed. :)

@Kobzol
Copy link
Member

Kobzol commented Sep 19, 2025

Hmm, I'd maybe like it more if we just marked all those tests as being LLVM only (or maybe had some "default test directives" per directory?), and then perhaps have a tidy check that ensures that indeed all tests are marked as such, to make the fact that these tests are being skipped more explicit.

That being said, we already have the opt-out for the assembly and codegen tests, so this doesn't seem terribly different from that.

I'd like to hear @jieyouxu's opinion, but otherwise looks fine to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-compiletest Area: The compiletest test runner 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)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants