<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_tiled_swapping@non-threaded - dmesg-warn - page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108686#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_tiled_swapping@non-threaded - dmesg-warn - page allocation failure"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108686">bug 108686</a>
from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=108686#c1">comment #1</a>)
<span class="quote">> Note it didn't cause a rendering error, so was just a transient allocation
> failure under heavy mempressure, so not really a bug, just the usual noise.
> Our only goal here is to make sure direct-reclaim is effective to never
> allow a preventable order-0 allocation failure.</span >
Shouldn't we hide this message then?
If not, this means that we would not catch anything happening when this failure
happens.
If this is OK, let's close with NOTABUG, but I will keep the issue in cibuglog.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>