585c27c717
We handle FAIL_TEST tests by simply inverting the success flag. The problem with this is, that if a FAIL_TEST fails by a SIGSEGV, it will be interpreted as passed. However, no code should ever cause a SEGV, or any other signal than ABRT. And even ABRT only in the case of an assert() that is meant to fail. We would probably need more sophistication for the FAIL_TEST cases. For now, just interpret any other signal than ABRT as a hard failure, regardless whether it is a TEST or FAIL_TEST. At least segfaults do not cause false passes anymore. Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| button-test.c | ||
| event-test.c | ||
| keyboard-test.c | ||
| Makefile.am | ||
| matrix-test.c | ||
| setbacklight.c | ||
| surface-global-test.c | ||
| surface-test.c | ||
| text-test.c | ||
| weston-test-client-helper.c | ||
| weston-test-client-helper.h | ||
| weston-test-runner.c | ||
| weston-test-runner.h | ||
| weston-test.c | ||
| weston-tests-env | ||