diff options
| author | jyn <github@jyn.dev> | 2024-12-01 21:47:20 -0500 |
|---|---|---|
| committer | jyn <github@jyn.dev> | 2024-12-01 21:47:20 -0500 |
| commit | 2f17ea0ff53ddedfa659b1173e5bbbd57fb0231d (patch) | |
| tree | 6c0fc1e63fc8b11f150bf99f0791e3e3a60c5a54 /tests/coverage/branch/lazy-boolean.coverage | |
| parent | 5bbbc0938cfeb3dbd348d5258ddb6025bc8398c7 (diff) | |
| download | rust-2f17ea0ff53ddedfa659b1173e5bbbd57fb0231d.tar.gz rust-2f17ea0ff53ddedfa659b1173e5bbbd57fb0231d.zip | |
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.
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.coverage')
0 files changed, 0 insertions, 0 deletions