<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL][bisected] multiple regressions in deqp-gles2@functional@shaders@keywords@reserved_keywords"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103604#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL][bisected] multiple regressions in deqp-gles2@functional@shaders@keywords@reserved_keywords"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103604">bug 103604</a>
from <span class="vcard"><a class="email" href="mailto:mark.a.janes@intel.com" title="Mark Janes <mark.a.janes@intel.com>"> <span class="fn">Mark Janes</span></a>
</span></b>
<pre>It seems to me that detecting regressions on blacklisted tests is desirable,
even if we are not required to pass them. It may be that some blacklisted
tests are wrong, but this bug is a data point that indicates tracking
pass->fail transitions will identify driver issues.
Tracking status for all the blacklisted tests will muddy the water for the mesa
CI, as we rely on CI test results to confirm that we pass conformance.
Ideally, we want the config files listing test failures to be empty.
Martin's ezbench system is a nice way to get this test coverage.</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>
</ul>
</body>
</html>