Bug 110920

Summary: [CI][SHARDS] igt@kms_color@pipe-[abc]-ctm-0-(25|75) - fail - Failed assertion: success
Product: DRI Reporter: Martin Peres <martin.peres>
Component: DRM/IntelAssignee: Uma Shankar <uma.shankar>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: ICL i915 features: display/color management

Description Martin Peres 2019-06-14 13:18:37 UTC
Enabling Multi-segmented-gamma for ICL[1] regresses igt@kms_color@pipe-[abc]-ctm-0-(25|75) due to unexpected rounding.

The problem needs to be addressed on the IGT side (comparing to different acceptable rounding values) and/or by re-implementing the test on top of pipe writeback.

In the mean time, let's have this bug to document the effort.

[1] https://patchwork.freedesktop.org/series/60126/

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard-iclb2/igt@kms_color@pipe-b-ctm-0-25.html

Starting subtest: pipe-B-ctm-0-25
(kms_color:1190) CRITICAL: Test assertion failure function run_tests_for_pipe, file ../tests/kms_color.c:985:
(kms_color:1190) CRITICAL: Failed assertion: success
Comment 1 Martin Peres 2019-06-14 13:19:40 UTC
Assigning Uma, since he is the author of multi-segmented gamma, and it is his responsibility to make sure that we do not regress our test coverage.
Comment 3 emersion 2019-06-28 07:41:26 UTC
This issue is hit every few hours.

User impact: test coverage issue, we're not able to check that Color Transformation matrices work properly.
Comment 5 CI Bug Log 2019-10-18 10:12:13 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL TGL: igt@kms_color@pipe-[abc]-ctm-0-(25|75) - fail - Failed assertion: success -}
{+ ICL TGL: igt@kms_color@pipe-[abcd]-ctm-0-(25|75) - fail - Failed assertion: success +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7103/shard-tglb3/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/shard-tglb4/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7106/shard-tglb1/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7108/shard-tglb5/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7110/shard-tglb1/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7111/shard-tglb6/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7113/shard-tglb7/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7115/shard-tglb6/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7116/shard-tglb7/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7118/shard-tglb6/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5232/shard-tglb1/igt@kms_color@pipe-d-ctm-0-75.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7121/shard-tglb1/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7121/shard-tglb2/igt@kms_color@pipe-d-ctm-0-75.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7124/shard-tglb5/igt@kms_color@pipe-d-ctm-0-25.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7124/shard-tglb6/igt@kms_color@pipe-d-ctm-0-75.html
Comment 6 Lakshmi 2019-10-18 10:17:06 UTC
(In reply to CI Bug Log from comment #5)
> A CI Bug Log filter associated to this bug has been updated:
> 
> {- ICL TGL: igt@kms_color@pipe-[abc]-ctm-0-(25|75) - fail - Failed
> assertion: success -}
> {+ ICL TGL: igt@kms_color@pipe-[abcd]-ctm-0-(25|75) - fail - Failed
> assertion: success +}
> 
> New failures caught by the filter:
> 
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7103/shard-tglb3/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/shard-tglb4/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7106/shard-tglb1/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7108/shard-tglb5/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7110/shard-tglb1/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7111/shard-tglb6/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7113/shard-tglb7/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7115/shard-tglb6/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7116/shard-tglb7/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7118/shard-tglb6/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5232/shard-tglb1/
> igt@kms_color@pipe-d-ctm-0-75.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7121/shard-tglb1/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7121/shard-tglb2/
> igt@kms_color@pipe-d-ctm-0-75.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7124/shard-tglb5/
> igt@kms_color@pipe-d-ctm-0-25.html
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7124/shard-tglb6/
> igt@kms_color@pipe-d-ctm-0-75.html

@Uma, Keeping TGL in view, do you think the severity of this issue remains same?
Comment 7 Martin Peres 2019-11-29 19:10:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/315.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.