<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] [Intel-GFX-CI] shards may get killed early, creating more incompletes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106127#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] [Intel-GFX-CI] shards may get killed early, creating more incompletes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106127">bug 106127</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 Tomi Sarvela from <a href="show_bug.cgi?id=106127#c9">comment #9</a>)
<span class="quote">> What kind of time limits are we talking about? Timeout affects all runs.
>
> I'd be more comfortable to exit igt early if we're close to the timeout.
> This would just get a note that not everything was tested due to limit, and
> no false positives from killing the job.</span >
That's indeed the idea! We would need to trust the IGT runner (and maybe write
support for an external watchdog), but that would definitely limit the amount
of random noise, which makes incomplete reports hard to act upon automatically.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>