diff options
| author | bors <bors@rust-lang.org> | 2023-04-20 15:15:17 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-04-20 15:15:17 +0000 |
| commit | a57fa08f483620c2b4f33c6b5dcdbbf2b4c08ad8 (patch) | |
| tree | 98ca0024b3b122374a126e60cdd76e4286212bae /tests/rustdoc-js-std/parser-errors.js | |
| parent | 791a7f22e3360bdbbc7fb7dab9f80e19fca4dd2b (diff) | |
| parent | a30171c63d921ac7437c8d0e49d96316b68c59c5 (diff) | |
| download | rust-a57fa08f483620c2b4f33c6b5dcdbbf2b4c08ad8.tar.gz | |
Auto merge of #110444 - ferrocene:comptest-lines, r=Mark-Simulacrum
Add compare-output-lines-by-subset flag to compiletest
For [ferrocene](github.com/ferrocene/) we have some compiletests that check the output of the cli arguments to the compiler, including printing things like the target list (`--print target-list`). Unfortunately those tend to change quite often so when we sync we end up with some outputs we have to re-bless constantly, even though the exact output doesn't really matter.
We added a new compiletest flag to aid writing these kinds of tests: `compare-output-lines-by-subset`. It checks whether the lines of the expected output are a subset (or equal) to the lines of the actual output. If the expected output is empty it will fail unless the actual output is also empty. We opened this PR hoping the flag might be helpful for other tests in the future (especially if CLI-related tests are added in the future in the rust-lang/rust repo itself).
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions