<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - regression on glsl shaders on BE architecture mesa-17.2.0-rc6"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102516#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - regression on glsl shaders on BE architecture mesa-17.2.0-rc6"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102516">bug 102516</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>If you have a working Apitrace trace, ezBench could be used to automatically
bisect which Mesa commits cause changes in rendering i.e. regresses it.
ezBench is here:
<a href="https://cgit.freedesktop.org/ezbench">https://cgit.freedesktop.org/ezbench</a>
You need to set up "user_parameters.sh" file so that ezBench can build Mesa &
run it with Apitrace, and have a folder with the apitrace trace file used for
render validation + a file which tells which frame in the trace is used for
comparison.
README tells how to setup & use ezBench. I will add some documentation on how
to do the Apitrace validation (to the example parameter file).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>