[Bug 108147] [CI][SHARDS] igt at kms_color@pipe-[abc]-ctm-max - fail - Failed assertion: test_pipe_ctm(data, primary, red_green_blue, full_rgb, ctm)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 10 13:47:56 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=108147

--- Comment #14 from Martin Peres <martin.peres at free.fr> ---
The IGT patch is merged:

commit 64d0ff7247497ae6d726e4535fe74d4bb6ae914a (HEAD -> master, origin/master,
origin/HEAD)
Author: Uma Shankar <uma.shankar at intel.com>
Date:   Wed Apr 3 17:50:10 2019 +0530

    tests/kms_color: Fix CRC mismatch issues with ctm test

    Due to Gamma/Degamma limitation wrt representation of intermediate
    values between 0 and 1.0 causing rounding issues and inaccuracies,
    applying linear gamma affects crc. This patch fixes the same by
    making ctm max test independent of gamma/degamma.

    v2: Disable degamma/gamma programming for ctm max test as it
    leads to crc mimsmatch. Limiting it to this test case alone as
    other tests need it to be enabled, hence not touching those
    scenarios.

    v3: Fixed a fumble with compilation.

    v4: Disabling degamma and gamma for ctm max tests, after the logic
    in kernel has been updated by Ville's series.

    v5: Disabled gamma/degamma for all ctm tests as suggested by Ville.

    v6: Restricting disabling of linear gamma luts for ctm max test.
    Updated the commit message and comment as suggested by Daniel.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108147
    Signed-off-by: Uma Shankar <uma.shankar at intel.com>
    Acked-by: Daniel Vetter <daniel.vetter at ffwll.ch>

Uma, please do the same when the kernel patch lands and then you can close the
bug. I'll close it in cibuglog when I can verify this is indeed fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190410/0ea42647/attachment.html>


More information about the intel-gfx-bugs mailing list