<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@gem_ctx_engines@independent - fail - Engine instance [2] executed too late" href="https://bugs.freedesktop.org/show_bug.cgi?id=110987#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@gem_ctx_engines@independent - fail - Engine instance [2] executed too late" href="https://bugs.freedesktop.org/show_bug.cgi?id=110987">bug 110987</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>There's a danger here as the test assumes in-order execution without explicit fencing (or else it is hard to say that each channel is independent), but we may trigger a timeslice evaluation in the middle and reorder. The goal of the test is to say that the engine[] are distinct and have no inherent common timeline (i.e. they all have their own rings and timelines). So we set them up with a fence that encourages them to execute in the opposite order to submission. Easiest way forward then would be to trickle feed the fences.</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>