On CI_DRM_2993, the machine shard-snb4 generated the following error when running igt@tools_test@check_dmesg: (tools_test:1497) CRITICAL: Test assertion failure function __real_main82, file tools_test.c:142: (tools_test:1497) CRITICAL: Failed assertion: !kmsg_check("*ERROR*") (tools_test:1497) CRITICAL: Last errno: 9, Bad file descriptor Full logs: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2993/shard-snb4/igt@tools_test@check_dmesg.html
It opens dmesg and checks for a pre-existing error. It is not a test, but a precheck. It should be removed from the test list as its duties are part of the test runner.
commit 8ec924498d32f51ab303a8ec9dae339919a5931c Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Sep 7 19:26:54 2017 +0100 igt/tools_test: Remove dmesg subtest It's a silly test. If fails if there is an *ERROR* in the dmesg ringbuf, so it neither is testing that errors are generated as expected, and as a pre-check it can only see what's at the end of the dmesg and may miss earlier faults. As a test it just randomly fails; worse than useless. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by: Martin Peres <martin.peres@linux.intel.com>
Thanks Chris!We wanted to run the others bug not inflight, once the new test stops killing the kernel, we should be ok to run all of gem_eio (or right now if killing the kernel with an oops and
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.