Skip to content

Commit e686abe

Browse files
Rollup merge of #150524 - test-build-std, r=jieyouxu,kobzol
Test that -Zbuild-std=core works on a variety of profiles See [#t-infra > Non-blocking testing for -Zbuild-std?](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-blocking.20testing.20for.20-Zbuild-std.3F/with/565837190) for some background. This is an incredibly CPU-hungry run-make-cargo test, but at least on my desktop the entire suite only takes a minute.
2 parents 8320018 + 8cbc21d commit e686abe

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

src/tests/compiletest.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,10 @@ The following test suites are available, with links for more information:
7878

7979
[`run-make`](#run-make-tests) are general purpose tests using Rust programs.
8080

81+
### The build-std test suite
82+
83+
[`build-std`](#build-std-tests) test that -Zbuild-std works.
84+
8185
### Rustdoc test suites
8286

8387
| Test suite | Purpose |
@@ -429,6 +433,12 @@ use cases that require testing in-tree `cargo` in conjunction with in-tree `rust
429433
The `run-make` test suite does not have access to in-tree `cargo` (so it can be the
430434
faster-to-iterate test suite).
431435

436+
### `build-std` tests
437+
438+
The tests in [`tests/build-std`] check that `-Zbuild-std` works. This is currently
439+
just a run-make test suite with a single recipe. The recipe generates test cases
440+
and runs them in parallel.
441+
432442
#### Using Rust recipes
433443

434444
Each test should be in a separate directory with a `rmake.rs` Rust program,

0 commit comments

Comments
 (0)