<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add tests checking how stable the CRCs are"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110754">110754</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Add tests checking how stable the CRCs are
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>IGT
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>arkadiusz.hiler@intel.com
</td>
</tr></table>
<p>
<div>
<pre>Such test can be made part of BAT to give us overview of the health of pipe
CRCs.
Initial idea:
1. run collecting CRCs
2. pull off the chaos monkey doing hotplugs, workloads, etc
3. make sure that CRC is stable
This way we will know which platforms suffer from unstable CRC and we can
filter out all of the CRC mismatches using CI buglog.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>