<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [i965 Bisected]ES2-CTS.gtf.GLCoverage.CoverageGL fails due to enable GL_RGB and GL_RGBA"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87211#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [i965 Bisected]ES2-CTS.gtf.GLCoverage.CoverageGL fails due to enable GL_RGB and GL_RGBA"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87211">bug 87211</a>
from <span class="vcard"><a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> <span class="fn">Ian Romanick</span></a>
</span></b>
<pre>(In reply to Eduardo Lima Mitev from <a href="show_bug.cgi?id=87211#c1">comment #1</a>)
<span class="quote">> The offending patch explicitly checks for a GLES3 context. If the failing
> test is a GLES2 as it seems, then it is not clear why is picking the invalid
> enums.
>
> Can we confirm the test is actually running a GLES2 profile?
>
> I will take a closer look.</span >
ES3 contexts are supposed to be backwards compatible with ES2. On platforms
that support ES3, Mesa (and other implementations?) always gives an ES3
context.</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>