<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@gem_exec_big - incomplete - Softdog" href="https://bugs.freedesktop.org/show_bug.cgi?id=105555#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@gem_exec_big - incomplete - Softdog" href="https://bugs.freedesktop.org/show_bug.cgi?id=105555">bug 105555</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Marta Löfstedt from <a href="show_bug.cgi?id=105555#c3">comment #3</a>) > (In reply to Chris Wilson from <a href="show_bug.cgi?id=105555#c2">comment #2</a>) > > Imo, this is a bug in CI for using owatch. > > We have to limit the runtime if your test can't make it in the timing budget > they belong to the blacklist That is not a bug in the test or kernel though. That is a limitation imposed by CI and needs to be reported as such, or rather handled entirely by CI since that wants to redefine tests to suite itself rather than the intent of the test. In this case owatch is entirely the wrong tool; nothing is expected to be on the output yet the test is still running perfectly fine. As a watchdog, owatch fails for this test.</pre> </div> <hr> You are receiving this mail because: <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>