<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] igt@gem_wait@wait-default - fail - Failed assertion: wait.timeout_ns > 0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106125">bug 106125</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;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WORKSFORME
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI] igt@gem_wait@wait-default - fail - Failed assertion: wait.timeout_ns > 0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106125#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI] igt@gem_wait@wait-default - fail - Failed assertion: wait.timeout_ns > 0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106125">bug 106125</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>Warning be silenced:
commit f772d9a910130b3aec8efa4f09ed723618fae656 (HEAD, upstream/master)
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Wed May 2 12:11:26 2018 +0100
igt/gem_wait: Relax assertion for wait completion
When waiting for a finite batch, all that we require is that the batch
completes. If it takes the full second (or longer) for us to wake up and
notice the completed batch is immaterial, so only assert that we don't
report an infinite timeout afterwards.
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Reviewed-by: Joonas Lahtinen <<a href="mailto:joonas.lahtinen@linux.intel.com">joonas.lahtinen@linux.intel.com</a>>
We can still get a timer error if the spin_set_timeout() doesn't fire within 1s
(target is 0.5s), but we no longer trigger a warning (as in this case) when we
don't wake up within 1s (due to whatever scheduling latency) but have detected
the completed batch (or we wouldn't wake up at all... except stray signals?)</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>
</ul>
</body>
</html>