[Bug 108228] [CI][SHARDS] igt@* - fail - Failed assertion: !mismatch (happened all at once)

[bugzilla-daemon at freedesktop.org]

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

Matt Roper <matthew.d.roper at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Matt Roper <matthew.d.roper at intel.com> ---
The original logs for this bug aren't available anymore, but based on the
description is sounds like CRC's just completely stopped working properly on
one specific run at the time this was filed (which is indeed very suspicious). 
Looking through the CI bug log results, it doesn't appear that we've had
another instance of everything breaking at once.

The buglog filter for this ticket is currently matching any kind of CRC
mismatch that happens on a SKL platform, which is probably catching things that
really should be broken out into separate bugs that can be analyzed
independently.  Going through the recent failures caught by the filter I see:
 * failures of igt at kms_flip_tiling@flip-changes-tiling-yf used to happen
periodically, but those are now captured more precisely by bug 108303 (CI issue
786)
 * failures of igt at kms_atomic_transition@1x-modeset-transitions-nonblocking
happened six months ago, but should probably be re-assigned to bug 105703 (CI
issue 284) instead of this one.
 * failures for kms_color at pipe-[abc]-gamma (most recent 6 months ago), but
should be re-assigned to bug 104782 (CI issue 185), although it sounds like
that bug itself may need to be split into separate ICL and non-ICL bugs
 * kms_mmap_write_crc --- same story; see fdo bug 103286

Given that we only seem to be catching items that should really be picked up by
the filters for other defects, I think it makes sense to close down this bug so
that we'll have more fine-grained bug filtering for CRC mismatches on SKL.

-- 
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/20190917/0d233ee4/attachment.html>