<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [many][EXT] igt@gem_streaming_writes tests incomplete in CI" href="https://bugs.freedesktop.org/show_bug.cgi?id=100335#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [many][EXT] igt@gem_streaming_writes tests incomplete in CI" href="https://bugs.freedesktop.org/show_bug.cgi?id=100335">bug 100335</a> from <a class="email" href="mailto:yann.argotti@intel.com" title="yann <yann.argotti@intel.com>"> yann</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=100335#c2">comment #2</a>) > What test failures? Don't confuse an incomplete (this bug) with a failure or > a CI enforced timeout. First of all, bug must not be closed w/o any explanation or justification. This is what it is happening here. Then this is correct that we have still various issue types linked to these test runs (not just going to the example that Jani is pointing out: batch-gtt) and to be accurate, avoid confusion, I agree with you, "Incomplete" state must be clearly defined to not misinterpret results.</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 QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>