<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][RESUME]igt@gem_persistent_relocs@interruptible - timeout - Code: Bad RIP value." href="https://bugs.freedesktop.org/show_bug.cgi?id=112271#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][RESUME]igt@gem_persistent_relocs@interruptible - timeout - Code: Bad RIP value." href="https://bugs.freedesktop.org/show_bug.cgi?id=112271">bug 112271</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Nothing too suspicious, looks to be a normal timeout for a slow test. I think we can do better in igt_runner to distinguish between suspicious timeouts and boring ones. Obviously, we can push the taint check earlier so any BUG_ON is immediately failed. Then we can check how it is responding to the signals, i.e. if it cleans up immediately on SIGQUIT, it's just a regular timeout. But if some processes are still stuck after SIGKILL, we have a deadlock on our hands.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>