diff options
| author | bors <bors@rust-lang.org> | 2024-07-11 00:56:46 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-07-11 00:56:46 +0000 |
| commit | e1f45a1442bb373429b6b0838e8ef806ddddfeef (patch) | |
| tree | 9ca606b35a8f96ac56c22673d95fbb6e12161c63 /compiler/rustc_middle/src | |
| parent | 3ad5f459b35769b8ad9f0b364d3dabb3721b9117 (diff) | |
| parent | 2adfa147d7cf07810f2d1658b482b8e44bef7e5b (diff) | |
| download | rust-e1f45a1442bb373429b6b0838e8ef806ddddfeef.tar.gz rust-e1f45a1442bb373429b6b0838e8ef806ddddfeef.zip | |
Auto merge of #127538 - Oneirical:the-sacred-tests, r=jieyouxu
Migrate `issue-83112-incr-test-moved-file`, `type-mismatch-same-crate-name` and `issue-109934-lto-debuginfo` `run-make` tests to rmake or ui Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). I have noticed that the new UI test `debuginfo-lto-alloc` is outputting artifacts that aren't getting cleaned up because of its `-C incremental`. That might be the justification needed to keep it as a run-make test? Try it on: // try-job: test-various // previously passed try-job: armhf-gnu try-job: aarch64-apple try-job: x86_64-msvc
Diffstat (limited to 'compiler/rustc_middle/src')
0 files changed, 0 insertions, 0 deletions