-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Closed
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.O-cskyTarget: glaCSKY above covers over me~Target: glaCSKY above covers over me~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
In tests/ui/abi/compatibility.rs
we're trying to test the ABI adjustment logic of all targets. This generally works as the test is no_core and LLVM has backends for all targets available -- except it does not seem possible to test the csky target that way. Trying to add the usual needs-llvm-components: csky
leads to an error from tidy:
/checkout/tests/ui/abi/compatibility.rs: revision csky specifies unknown LLVM component `csky`
The test passes just fine locally, so it seems like at least the downloaded LLVM has the csky
component. I don't know why it was not added to tidy's KNOWN_LLVM_COMPONENTS
list.
Cc @Dirreke
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.O-cskyTarget: glaCSKY above covers over me~Target: glaCSKY above covers over me~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)
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
workingjubilee commentedon May 29, 2024
cc @erikdesjardins but also I think this was just an oversight.
RalfJung commentedon May 29, 2024
FWIW if one just adds this to a test it does pass on CI
but of course it may just be silently ignored, hard to say whether the test actually runs... this
needs-llvm-components
stuff makes tests quite fragile. :/workingjubilee commentedon May 29, 2024
Yeah, the tidy check was added to reduce the fragility because a lot of people were giving names other than the LLVM component's name, like riscv64 instead of riscv, etc.
RalfJung commentedon May 29, 2024
The remaining question then is, how sure are we that the components accepted by tidy are all available on some CI runner?
RalfJung commentedon May 29, 2024
Also, something else must have been going on... I disabled this test before that sanity check was added to tidy.
Sadly the logs for this failure are already gone.
Auto merge of rust-lang#125702 - workingjubilee:tell-tidy-about-csky,…
Auto merge of rust-lang#125702 - workingjubilee:tell-tidy-about-csky,…