diff options
| author | bors <bors@rust-lang.org> | 2024-04-27 18:45:51 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-27 18:45:51 +0000 |
| commit | 825e831dc30e498abcdc4ad1a521658ff84f09d4 (patch) | |
| tree | 9408ba6ceeccbd6478898f0e11bfa55c03102c4f /compiler/rustc_codegen_gcc/example/example.rs | |
| parent | 61a1dbd751ab7f3c973be17d7ff3948ffda07c6e (diff) | |
| parent | babead5b586f8294b789a7fba252491b866aee61 (diff) | |
| download | rust-825e831dc30e498abcdc4ad1a521658ff84f09d4.tar.gz rust-825e831dc30e498abcdc4ad1a521658ff84f09d4.zip | |
Auto merge of #124405 - RalfJung:miri-core-alloc-tests, r=clubby789
miri core/alloc tests: do not test a 2nd target check-aux seems to be one of the slowest runners since we started running standard library tests in Miri on it. So maybe it'd be better to reduce test coverage a bit by not doing cross-target testing of core and alloc? I don't recall finding target-specific issues in these libraries ever (and we still have the extra test coverage via our [out-of-tree nightly tests](https://github.com/rust-lang/miri-test-libstd)). This gives us more buffer to deal with the fact that the number of tests we run will only grow over time. Cc `@rust-lang/miri` `@rust-lang/infra`
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/example.rs')
0 files changed, 0 insertions, 0 deletions