@@ -23,12 +23,11 @@ In order to change how a single test is tested, you can add various `//@` commen
23
23
Any other comments will be ignored, and all ` //@ ` comments must be formatted precisely as
24
24
their command specifies, or the test will fail without even being run.
25
25
26
- * ` //@ignore-XXX ` avoids running the test on targets whose triple contains ` XXX `
27
- * ` XXX ` can also be one of ` 64bit ` , ` 32bit ` or ` 16bit `
28
- * ` XXX ` can also be ` on-host ` , which will only run the test during cross compilation testing.
29
- * ` //@only-XXX ` avoids running the test on targets whose triple ** does not** contain ` XXX `
30
- * ` XXX ` can also be one of ` 64bit ` , ` 32bit ` or ` 16bit `
31
- * ` XXX ` can also be ` on-host ` , which will not run the test during cross compilation testing
26
+ * ` //@ignore-C ` avoids running the test when condition ` C ` is met.
27
+ * ` C ` can be ` target-XXX ` , which checks whether the target triple contains ` XXX ` .
28
+ * ` C ` can also be one of ` 64bit ` , ` 32bit ` or ` 16bit ` .
29
+ * ` C ` can also be ` on-host ` , which will only run the test during cross compilation testing.
30
+ * ` //@only-C ` ** only** runs the test when condition ` C ` is met. The conditions are the same as with ` ignore ` .
32
31
* ` //@stderr-per-bitwidth ` produces one stderr file per bitwidth, as they may differ significantly sometimes
33
32
* ` //@error-pattern: XXX ` make sure the stderr output contains ` XXX `
34
33
* ` //@revisions: XXX YYY ` runs the test once for each space separated name in the list
@@ -46,5 +45,5 @@ their command specifies, or the test will fail without even being run.
46
45
47
46
## Significant differences to compiletest-rs
48
47
49
- * ` ignore-* ` and ` only-* ` opereate solely on the triple, instead of supporting things like ` macos `
48
+ * ` ignore-target- * ` and ` only-target -* ` opereate solely on the triple, instead of supporting things like ` macos `
50
49
* only ` //~ ` comments can be individualized per revision
0 commit comments