<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:arkadiusz.hiler@intel.com" title="Arek Hiler <arkadiusz.hiler@intel.com>"> <span class="fn">Arek Hiler</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110246">bug 110246</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>[CI][SHARDS] igt@gem_mocs_settings@mocs-rc6-blt - incomplete - Jenkins killed the machine when it shouldn't
</td>
<td>[CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110246#c27">Comment # 27</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110246">bug 110246</a>
from <span class="vcard"><a class="email" href="mailto:arkadiusz.hiler@intel.com" title="Arek Hiler <arkadiusz.hiler@intel.com>"> <span class="fn">Arek Hiler</span></a>
</span></b>
<pre>(In reply to Jani Saarinen from <a href="show_bug.cgi?id=110246#c22">comment #22</a>)
<span class="quote">> 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?</span >
I believe this is the patch:
commit a52cc643cfe6733465cfc9ccb3d21cbdc4fd7506
Author: Petri Latvala <<a href="mailto:petri.latvala@intel.com">petri.latvala@intel.com</a>>
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 <<a href="mailto:petri.latvala@intel.com">petri.latvala@intel.com</a>>
Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
The issue still occurs:
<a href="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_6005/fi-icl-u2/igt@gem_exec_basic@basic-blt.html</a>
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6012/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</a>
Reproduction rate seems to be still in the same ballpark.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>