<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI][SHARDS] igt@gem_exec_big@single - dmesg-fail / incomplete - gem_exec_big: page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110260">bug 110260</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;">Resolution</td>
<td>---
</td>
<td>WORKSFORME
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI][SHARDS] igt@gem_exec_big@single - dmesg-fail / incomplete - gem_exec_big: page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110260#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI][SHARDS] igt@gem_exec_big@single - dmesg-fail / incomplete - gem_exec_big: page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110260">bug 110260</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>It's the same old page allocation failure under the slightest bit of file
system activity (this case seems to be caused by the Java process continuing to
allocate while igt believes it can use all available memory being the sole
task). Swept under the carpet (go look at the other page allocation failures)
because ignorance is bliss.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>