Via #126155, I discovered that the //@ needs-matching-clang compiletest header is a lot more strict than one might assume from its name.
Tests with this header are not run by default, regardless of whether a “matching clang” is available or not. Instead, they only run if environment variable RUSTBUILD_FORCE_CLANG_BASED_TESTS is set.
The only test job that sets this variable is x86_64-gnu-debug, but that job currently doesn't actually run any tests! (Though that might change as a result of #126155.)
@rustbot label +A-compiletest +A-testsuite
Via #126155, I discovered that the
//@ needs-matching-clangcompiletest header is a lot more strict than one might assume from its name.Tests with this header are not run by default, regardless of whether a “matching clang” is available or not. Instead, they only run if environment variable
RUSTBUILD_FORCE_CLANG_BASED_TESTSis set.The only test job that sets this variable is
x86_64-gnu-debug, but that job currently doesn't actually run any tests! (Though that might change as a result of #126155.)@rustbot label +A-compiletest +A-testsuite