Bug 103207 - [CI] igt@kms_atomic_transition@1x-modeset-transitions* - Fail - CRC mismatch
Summary: [CI] igt@kms_atomic_transition@1x-modeset-transitions* - Fail - CRC mismatch
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Whiteboard: ReadyForDev
Depends on:
Blocks: 105978
  Show dependency treegraph
Reported: 2017-10-11 07:04 UTC by Marta Löfstedt
Modified: 2018-06-19 22:18 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: display/Other


Description Marta Löfstedt 2017-10-11 07:04:24 UTC
CI_DRM_3206 APL-shards  igt@kms_atomic_transition@1x-modeset-transitions

(kms_atomic_transition:1527) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:346:
(kms_atomic_transition:1527) igt-debugfs-CRITICAL: Failed assertion: !mismatch
Subtest 1x-modeset-transitions failed.

Comment 1 Marta Löfstedt 2017-12-01 09:40:09 UTC
last seen: 2017-11-01 / 144 runs ago
Comment 2 Marta Löfstedt 2018-01-05 07:28:44 UTC
Reopened this since we hit:


(kms_atomic_transition:1431) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:356:
(kms_atomic_transition:1431) igt-debugfs-CRITICAL: Failed assertion: !mismatch
Subtest 1x-modeset-transitions-fencing failed.
Comment 3 Marta Löfstedt 2018-01-05 07:29:22 UTC
Note igt@kms_atomic_transition@1x-modeset-transitions is still green.
Comment 4 Francesco Balestrieri 2018-06-12 12:37:02 UTC
Last seen one month ago according to cibuglogger.
Comment 5 Martin Peres 2018-06-19 22:18:17 UTC
(In reply to Francesco Balestrieri from comment #4)
> Last seen one month ago according to cibuglogger.

Indeed. This used to happen roughly every one to two weeks, and now it has not happened since CI_DRM_4172_full (1 month, 1 week / 668 runs ago). Closing!

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.