[Bug 110246] [CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=110246

Arek Hiler <arkadiusz.hiler at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[CI][SHARDS]                |[CI][SHARDS] Random tests -
                   |igt at gem_mocs_settings@mocs- |incomplete - empty
                   |rc6-blt - incomplete -      |stdout/stderr/dmesg -
                   |Jenkins killed the machine  |watchdog0: watchdog did not
                   |when it shouldn't           |stop!

--- Comment #27 from Arek Hiler <arkadiusz.hiler at intel.com> ---
(In reply to Jani Saarinen from comment #22)
> Petri mentioned there has been some changes made on CI side so that omm
> killer do not kill java...So has this been seen after this change?

I believe this is the patch:

commit a52cc643cfe6733465cfc9ccb3d21cbdc4fd7506
Author: Petri Latvala <petri.latvala at intel.com>
Date:   Thu Apr 11 12:40:12 2019 +0300

    runner: Make sure oom-killer doesn't kill the runner

    Tests that eat all of the RAM and then some to invoke the oom-killer
    deliberately sometimes cause extra casualties. Make sure the runner
    stays alive.

    Signed-off-by: Petri Latvala <petri.latvala at intel.com>
    Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>

The issue still occurs:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6005/fi-icl-u2/igt@gem_exec_basic@basic-blt.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6012/fi-icl-u2/igt@gem_exec_basic@basic-blt.html

Reproduction rate seems to be still in the same ballpark.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190430/d175bc0d/attachment.html>