| commit | 4eafb9748b9f850558837ea8e08677a784c1d72b | |
| author | Hans-Peter Nilsson <hp@axis.com> | |
| Wed, 22 Nov 2023 17:52:34 +0000 (22 18:52 +0100) | ||
| committer | Hans-Peter Nilsson <hp@bitrange.com> | |
| Thu, 23 Nov 2023 23:21:31 +0000 (24 00:21 +0100) | ||
| tree | af3d393a5d7bb45263849e0878b8b7c751c8d5a7 | treesnapshot (tar.gz zip) |
| parent | 071dadb728d0ed712af26f81fbe470b266a55607 | commitdiff |
contrib/regression/btest-gcc.sh: Optionally handle XPASS.
Tests with keys that match both PASS, FAIL (or now
optionally XPASS), count as fail. XPASSes were previously
ignored. Handling them as FAIL seems the most useful
alternative, but not counting XPASSes may be deliberate.
It's also a matter of compatibility, so make it optional.
Attempts to use --handle-xpass-as-fail was previously
flagged as a usage error. If you pass it now, on state with
previous mixed XPASS and PASS results but doesn't change in
this run, the XPASS is discovered as a (new) regression.
For new XPASSing tests, it's handled as a new FAIL.
* btest-gcc.sh (--handle-xpass-as-fail): New option.
Tests with keys that match both PASS, FAIL (or now
optionally XPASS), count as fail. XPASSes were previously
ignored. Handling them as FAIL seems the most useful
alternative, but not counting XPASSes may be deliberate.
It's also a matter of compatibility, so make it optional.
Attempts to use --handle-xpass-as-fail was previously
flagged as a usage error. If you pass it now, on state with
previous mixed XPASS and PASS results but doesn't change in
this run, the XPASS is discovered as a (new) regression.
For new XPASSing tests, it's handled as a new FAIL.
* btest-gcc.sh (--handle-xpass-as-fail): New option.
| contrib/regression/btest-gcc.sh | diffblobblamehistory |