<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_mocs_settings@mocs-rc6-blt - incomplete - Jenkins killed the machine when it shouldn't" href="https://bugs.freedesktop.org/show_bug.cgi?id=110246#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@gem_mocs_settings@mocs-rc6-blt - incomplete - Jenkins killed the machine when it shouldn't" href="https://bugs.freedesktop.org/show_bug.cgi?id=110246">bug 110246</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Lakshmi from <a href="show_bug.cgi?id=110246#c19">comment #19</a>) > This is a CI issue like how we run the tests. Random tests are failed as > incompletes. > The impact of this bug is that we don't test results from the incompletes. > We can not know the user impact at the moment unless the bug is fixed, e.g > we can't catch regressions. > > All the failures in this bugs are seen only on ICL. What Lakshmi was trying to say is that we cannot know the health of ICL until this bug is fixed, because we cannot distinguish if an incomplete comes because of a platform issue or a CI system issue. We need to investigate why ICL is behaving so badly compared to the other shards or RVPs (or maybe we just try too hard compared to other platforms where we just ignore all incompletes), and experiment with potential fixes.</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>