diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2018-11-13 17:19:10 +0000 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2018-11-27 13:01:10 +0000 |
commit | 0be3f3e7c1613dcaf27267fce778025ea46a36c1 (patch) | |
tree | 9dae44cfb9bb5034c5331595e0c8c4898202f7f8 /benchmarks | |
parent | 760106abf8f0ab8683fd61c858f1fb77686e5405 (diff) |
runner: Treat dmesg warnings as pure warnings
I have whinged on for ages about the dmesg-warnings being an expected
part of kernel testing (where else is the kernel meant to log its
errors?) and should be treated the same as our stderr for the test. That
is if a test fails, it fails and does not need to be conflated with
whether or not there was a dmesg warning (just as the test saying why it
failed on stderr does not need flagging), and that a passing test with a
dmesg warning is simply a warn.
The effect is that we simply remove the "dmesg-" flagging from results
names, as the err/dmesg output is simply collated for the error report
already.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Martin Peres <martin.peres@linux.intel.com>
Diffstat (limited to 'benchmarks')
0 files changed, 0 insertions, 0 deletions