diff options
author | Thomas Haller <thaller@redhat.com> | 2023-09-08 00:07:13 +0200 |
---|---|---|
committer | Florian Westphal <fw@strlen.de> | 2023-09-08 11:50:41 +0200 |
commit | 55fe071cd1939cca2294ceeef639625c3d81abeb (patch) | |
tree | a0942db9eaf7a48096bad49232370205b64c1b3e /tests/shell/README | |
parent | 20776aa335a7835a12a06c36b1a0d816e837a7c8 (diff) |
tests/shell: cleanup result handling in "test-wrapper.sh"
The previous code was mostly correct, but hard to understand.
Rework it.
Also, on failure now always write "rc-failed-exit", which is the exit
code that "test-wrapper.sh" reports to "run-test.sh". Note that this
error code may not be the same as the one returned by the TEST binary.
The latter you can find in one of the files "rc-{ok,skipped,failed}".
In general, you can search the directory with test results for those
"rc-*" files. If you find a "rc-failed" file, it was counted as failure.
There might be other "rc-failed-*" files, depending on whether the diff
failed or kernel got tainted.
Also, reserve all the error codes 118 - 124 for the "test-wrapper.sh".
For example, 124 means a dump difference and 123 means kernel got
tainted. In the future, 122 will mean a valgrind error. Other numbers
are not reserved. If a test command fails with such an reserved code,
"test-wrapper.sh" modifies it to 125, so that "run-test.sh" does not get
the wrong idea about the failure reason. This is not new in this patch,
except that the reserved range was extended for future additions.
Signed-off-by: Thomas Haller <thaller@redhat.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'tests/shell/README')
0 files changed, 0 insertions, 0 deletions