diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2025-07-26 22:42:38 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-26 22:42:38 -0400 |
| commit | 2c0a33178190ff4e577afda2b89a535c4dc2dcf8 (patch) | |
| tree | c14b56f89d9c7fb26f367f10d8c63e86dc003f32 /tests/rustdoc-js-std/doc-alias-use.js | |
| parent | e04daf98f145bd8b6d64ef11884503d600043ca6 (diff) | |
| parent | 3dac888c866ad76e43e6e7fa664805e009570eb4 (diff) | |
| download | rust-2c0a33178190ff4e577afda2b89a535c4dc2dcf8.tar.gz rust-2c0a33178190ff4e577afda2b89a535c4dc2dcf8.zip | |
Rollup merge of #144464 - Kobzol:x-test-default, r=jieyouxu
Only run bootstrap tests in `x test` on CI Discussed at https://rust-lang.zulipchat.com/#narrow/channel/122652-new-members/topic/Linux.20Distribution/with/530839642. The bootstrap tests can be sensitive of the environment where they are executed. And now that they are executed very early in the test pipeline, it can be annoying for people who just try to do `x test` when it fails on bootstrap tests. We could move the bootstrap tests back to the end of the `x test` pipeline, but then it would just fail later. I'd prefer to only run them on CI by default. Fixes: https://github.com/rust-lang/rust/issues/143973
Diffstat (limited to 'tests/rustdoc-js-std/doc-alias-use.js')
0 files changed, 0 insertions, 0 deletions