<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_* - fail - Failed assertion: ret == 0, Last errno: 22, Invalid argument" href="https://bugs.freedesktop.org/show_bug.cgi?id=109052#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_* - fail - Failed assertion: ret == 0, Last errno: 22, Invalid argument" href="https://bugs.freedesktop.org/show_bug.cgi?id=109052">bug 109052</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>ICL is failing constantly on igt@kms_plane_scaling@pipe-[abc]-scaler-with-rotation, which indicates that the test is trying to do something that the kernel refuses. This is either a test issue that needs to be fixed, or the kernel not providing what it should. As for the customer impact, the worst thing that can be is that the feature is broken because it is not tested, but since the feature is not exactly the most common use case, then a priority is already high-enough. As for the random failures we see on the other platforms, these are likely due to previous tests leaving pipes and planes enabled, and the failing test having failed to reset the state of the machine to an expected one. The fix for this is likely to reset the state of the machine in the lib igt for every KMS test, in order to provide consistency between tests. The customer impact is that we could let some regressions in that lead to more consistent failing, as noone is looking at the changes in reproduction rate and CI BUg log will not warn us about it ... yet. So, high priority it is again!</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>