diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2024-12-02 17:36:05 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-02 17:36:05 +0100 |
| commit | 15fda1e90bae7169e401aa5c5865a26511ac69c0 (patch) | |
| tree | b59f4ebfd71de276d0e7e12ddb2b19ecdf020a05 /tests/coverage/branch/lazy-boolean.coverage | |
| parent | 7fdbde0e18b24fa75ffc8e6fc1c33d65457487f4 (diff) | |
| parent | 2f17ea0ff53ddedfa659b1173e5bbbd57fb0231d (diff) | |
| download | rust-15fda1e90bae7169e401aa5c5865a26511ac69c0.tar.gz rust-15fda1e90bae7169e401aa5c5865a26511ac69c0.zip | |
Rollup merge of #133725 - jyn514:remove-compare-output-subset, r=jieyouxu
Remove `//@ compare-output-lines-by-subset` There was only ever one test which used this flag, and it was removed in https://github.com/rust-lang/rust/pull/132244. I think this is a bad flag that should never have been added; comparing by subset makes the test failures extremely hard to debug. Any test that needs complicated output filtering like this should just use run-make instead. Note that this does not remove the underlying comparison code, because it's still used if `runner` is set. I don't quite understand what's going on there, but since we still test on other platforms and in CI that the full output is accurate, I think it will be easier to debug than a test that uses compare-by-subset unconditionally. rustc-dev-guide update PR: https://github.com/rust-lang/rustc-dev-guide/pull/2151
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.coverage')
0 files changed, 0 insertions, 0 deletions