<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_color@pipe-[abc]-ctm-$color-to-$color - fail - Failed assertion: test_pipe_ctm(data, primary, red_green_blue, .*, ctm)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107201#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_color@pipe-[abc]-ctm-$color-to-$color - fail - Failed assertion: test_pipe_ctm(data, primary, red_green_blue, .*, ctm)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107201">bug 107201</a> from <a class="email" href="mailto:uma.shankar@intel.com" title="Uma Shankar <uma.shankar@intel.com>"> Uma Shankar</a> <pre>Very nicely explained by Matt, this is exactly how these tests are designed and expected to behave. However for these random failures- This is in general a static behavior, the test if passed in 1 run should pass on stress as well. If any roundup or interpolation error is there, then it should come for every run. Since on the hardware highlighted in this Bugzilla it passes most of the time and fails in <10%, this points to some inconsistent update or a failed evasion, underrun etc. If any of this happens we may get a wrong crc and match will fail. So ideally this is not a color related issue as such but atomic update, underrun related behavior causing this test to fail inconsistently. Lets keep an eye on this issue with medium priority and bump up in case we see consistent failures. Note: There are failures in color test with ICL+ hardware and multi segmented gamma (high precision gamma), but that occurs consistently i/e all the time (100% reproducible). Those issues are being analyzed to find some WA and are being tracked separately.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>