Adds the crash, timeout and the dmesg-* statuses. Signed-off-by: Dylan Baker <[email protected]> --- README | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/README b/README index 055e8e4..e302ec3 100644 --- a/README +++ b/README @@ -217,21 +217,22 @@ Have a look at the results with a browser: The summary shows the 'status' of a test: - pass This test has completed successfully. + pass This test has completed successfully. - warn The test completed successfully, but something unexpected happened. - Look at the details for more information. + warn The test completed successfully, but something unexpected happened. + Look at the details for more information. - fail The test failed. + fail The test failed. - skip The test was skipped. + crash The test binary exited with a non-zero exit code -[Note: Once performance tests are implemented, 'fail' will mean that the test - rendered incorrectly or didn't complete, while 'warn' will indicate a - performance regression] -[Note: For performance tests, result and status will be different concepts. - While status is always restricted to one of the four values above, - the result can contain a performance number like frames per second] + skip The test was skipped. + + timeout The test binary ran longer than it was allocated to and was + forcably killed + +There are also dmesg-* statuses. These have the same meaning as above, but were +triggered by dmesg related messages. 4. Available test sets -- 2.1.2 _______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
