<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium@(hdmi|dp)-hpd-fast - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111045#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium@(hdmi|dp)-hpd-fast - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111045">bug 111045</a> from <a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>(In reply to emersion from <a href="show_bug.cgi?id=111045#c9">comment #9</a>) > (In reply to Imre Deak from <a href="show_bug.cgi?id=111045#c8">comment #8</a>) > > Not sure what you mean here. Hotplug uevents are handled already by all the > > tests (those are the events the test is waiting for), the handling just > > lacks the corresponding output enabling/disabling. > > No, hotplug events aren't handled by kms_chamelium. Instead, the tests poll > for the connector to become connected. See wait_for_connector. Oh, ok. Missed this fact. The solution for DP-alt in case of these tests is anyway (1) black-list them for the DP-alt machines, and then (2) add new tests that do the enabling/disabling when they detected the connector status via polling, or just disable the output for the whole duration of the subtest (and then restore the state to the pre-subtest state). (In reply to emersion from <a href="show_bug.cgi?id=111045#c10">comment #10</a>) > Well, depends on the tests I guess. Some tests use igt_hotplug_detected. Ok, so these will need the same handling as above (1) and optionally (2).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>