diff options
author | Julian Lettner <julian.lettner@apple.com> | 2019-11-12 08:24:26 -0800 |
---|---|---|
committer | Julian Lettner <julian.lettner@apple.com> | 2019-11-12 09:11:36 -0800 |
commit | 54a9b4c02ff57e9847e0c501578e51db6f73d3be (patch) | |
tree | 2d11119c5c50c1538e9ec639ed518861635d4bad /lldb/source/Plugins/SymbolFile/Breakpad/SymbolFileBreakpad.h | |
parent | 83dcb34b6bf4c175040b18d3e8c3c468418009fc (diff) | |
download | bcm5719-llvm-54a9b4c02ff57e9847e0c501578e51db6f73d3be.tar.gz bcm5719-llvm-54a9b4c02ff57e9847e0c501578e51db6f73d3be.zip |
[lit] Better/earlier errors for empty runs
Fail early, when we discover no tests at all, or filter out all of them.
There is also `--allow-empty-runs` to disable test to allow workflows
like `LIT_FILTER=abc ninja check-all`. Apparently `check-all` invokes
lit multiple times if certain projects are enabled, which would produce
unwanted "empty runs". Specify via `LIT_OPTS=--allow-empty-runs`.
There are 3 causes for empty runs:
1) No tests discovered. This is always an error. Fix test suite config
or command line.
2) All tests filtered out. This is an error by default, but can be
suppressed via `--alow-empty-runs`. Should prevent accidentally
passing empty runs, but allow the workflow above.
3) The number of shards is greater than the number of tests. Currently,
this is never an error. Personally, I think we should consider
making this an error by default; if this happens, you are doing
something wrong. I added a warning but did not change the behavior,
since this warrants more discussion.
Reviewed By: atrick, jdenny
Differential Revision: https://reviews.llvm.org/D70105
Diffstat (limited to 'lldb/source/Plugins/SymbolFile/Breakpad/SymbolFileBreakpad.h')
0 files changed, 0 insertions, 0 deletions