diff options
| author | Dylan Baker <dylanx.c.baker@intel.com> | 2014-10-17 14:52:13 -0700 |
|---|---|---|
| committer | Dylan Baker <dylanx.c.baker@intel.com> | 2014-10-28 19:45:25 -0700 |
| commit | c23caad79e273b34c3db1d231f3e44102a05762a (patch) | |
| tree | 74b29822ecce2533b2efd3b3f86242389b6f4f87 | |
| parent | 3f0253608c1dea38f5122c438c45859f766cf62d (diff) | |
README: Update result statuses
Adds the crash, timeout and the dmesg-* statuses.
v2: - fix some nits from Ken
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
| -rw-r--r-- | README | 23 |
1 files changed, 12 insertions, 11 deletions
@@ -214,21 +214,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 ran longer than its allotted time and was forcibly killed. + + +There are also dmesg-* statuses. These have the same meaning as above, but are +triggered by dmesg related messages. 4. Available test sets |