[Bug 108228] New: [CI][SHARDS] igt@* - fail - Failed assertion: !mismatch

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Oct 4 10:12:30 UTC 2018


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

            Bug ID: 108228
           Summary: [CI][SHARDS] igt@* - fail - Failed assertion:
                    !mismatch
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: martin.peres at free.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl5/igt@kms_flip_tiling@flip-changes-tiling-yf.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl9/igt@kms_pwrite_crc.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl9/igt@kms_mmap_write_crc.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl7/igt@kms_color@pipe-c-gamma.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl9/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking.html

Starting subtest: 1x-modeset-transitions-nonblocking
(kms_atomic_transition:1103) igt_debugfs-CRITICAL: Test assertion failure
function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392:
(kms_atomic_transition:1103) igt_debugfs-CRITICAL: Failed assertion: !mismatch
Subtest 1x-modeset-transitions-nonblocking failed.

I am filing one single bug because all of these failed only once on the same
run, and not after... This seems super suspicious.

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


More information about the intel-gfx-bugs mailing list