<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI][SHARDS] igt@* - fail - Failed assertion: !mismatch (happened all at once)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108228">bug 108228</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WORKSFORME
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI][SHARDS] igt@* - fail - Failed assertion: !mismatch (happened all at once)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108228#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - [CI][SHARDS] igt@* - fail - Failed assertion: !mismatch (happened all at once)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108228">bug 108228</a>
from <span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span></b>
<pre>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@kms_flip_tiling@flip-changes-tiling-yf used to happen
periodically, but those are now captured more precisely by <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@kms_flip_tiling@flip-(y-tiled|changes-tiling(-yf?)?) - fail - Failed assertion: !mismatch"
href="show_bug.cgi?id=108303">bug 108303</a> (CI issue
786)
* failures of igt@kms_atomic_transition@1x-modeset-transitions-nonblocking
happened six months ago, but should probably be re-assigned to <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI][DRMTIP] igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Test assertion failure function igt_display_commit_atomic - Failed assertion: ret == 0"
href="show_bug.cgi?id=105703">bug 105703</a> (CI
issue 284) instead of this one.
* failures for kms_color@pipe-[abc]-gamma (most recent 6 months ago), but
should be re-assigned to <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@kms_color@pipe-[abc]-*gamma - fail - CRC mismatch"
href="show_bug.cgi?id=104782">bug 104782</a> (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 <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@kms_mmap_write_crc - fail - CRC mismatch"
href="show_bug.cgi?id=103286">bug 103286</a>
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>