-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Some tests are incorrectly skipped for macOS CI #117721
Comments
My suggestion would be to have another flag that performs the same substring match. For example, using
|
If you don't want e.g., Does this help? |
@rustbot label O-macos |
This should work fine, feel free to re-open the issue if it doesn't help. |
We need to actually do this in our CI IMO before the issue should be closed. |
Yeah, makes sense. |
use `--exact` on `--skip` to avoid unintended substring matches Without the `--exact` flag, using `--skip tests/rustdoc` can unintentionally skip other tests that match as substrings such as `rustdoc-gui`, `rustdoc-js`, etc. For debugging, run: `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc` and `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc -- --exact` Resolves rust-lang#117721
use `--exact` on `--skip` to avoid unintended substring matches Without the `--exact` flag, using `--skip tests/rustdoc` can unintentionally skip other tests that match as substrings such as `rustdoc-gui`, `rustdoc-js`, etc. For debugging, run: `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc` and `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc -- --exact` Resolves rust-lang#117721 try-job: x86_64-apple-1
use `--exact` on `--skip` to avoid unintended substring matches Without the `--exact` flag, using `--skip tests/rustdoc` can unintentionally skip other tests that match as substrings such as `rustdoc-gui`, `rustdoc-js`, etc. For debugging, run: `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc` and `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc -- --exact` Resolves rust-lang#117721 try-job: x86_64-apple-1
Rollup merge of rust-lang#132979 - onur-ozkan:skip-exact, r=jieyouxu,tgross35 use `--exact` on `--skip` to avoid unintended substring matches Without the `--exact` flag, using `--skip tests/rustdoc` can unintentionally skip other tests that match as substrings such as `rustdoc-gui`, `rustdoc-js`, etc. For debugging, run: `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc` and `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc -- --exact` Resolves rust-lang#117721 try-job: x86_64-apple-1
use `--exact` on `--skip` to avoid unintended substring matches Without the `--exact` flag, using `--skip tests/rustdoc` can unintentionally skip other tests that match as substrings such as `rustdoc-gui`, `rustdoc-js`, etc. For debugging, run: `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc` and `./x.py --stage 2 test rustdoc-ui --skip tests/rustdoc -- --exact` Resolves rust-lang/rust#117721 try-job: x86_64-apple-1
CI specifies these two jobs for x86_64-apple-darwin:
rust/src/ci/github-actions/ci.yml
Lines 528 to 544 in 341efb1
Note these two lines (with padding I've added):
It appears that the intent was for the first job to run a subset of the tests and the second job to run the complementary subset. However, it seems that
--skip
performs a substring match while the list of directories is an exact match. This means that the tests inrustdoc-js
,rustdoc-json
, andrustdoc-ui
are never run on macOS CI — they are excluded by--skip
and never explicitly added back.Surprisingly, it seems that tests in
rustdoc-js-std
are run. That seems like a secondary bug as it isn't behaving the same.The text was updated successfully, but these errors were encountered: