<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BAT][SKL] igt@kms_flip@basic-flip-vs-dpms produces a dmesg-fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101167#c26">Comment # 26</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BAT][SKL] igt@kms_flip@basic-flip-vs-dpms produces a dmesg-fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101167">bug 101167</a>
from <span class="vcard"><a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> <span class="fn">Marta Löfstedt</span></a>
</span></b>
<pre>Also, remember that when the failing starts at for example
igt@kms_busy@basic-flip-default-c the we fail at a very different place
compared to the kms_flip fail. However, then we see from IGT:
(kms_busy:3941) igt-kms-WARNING: connector 48/eDP-1 has no modes
ssame hold true for the: igt@kms_pipe_crc_basic and igt@kms_cursor_legacy fails
that is going on on this machine after we have ended up in this state.
I discussed with Petri if IGT should skip when we end up in this "no modes"
state. But I believe Petri doesn't want the IGT skip to be used for bad states
that has occurred in test run-time. Such as the skip by kms_flip.
The suggestion would be to implement an IGT abort exit criteria instead of
using the IGT skip for different reasons.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>