<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CTS regression] mesa af2723 breaks GL Conformance for debug extension"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93048#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CTS regression] mesa af2723 breaks GL Conformance for debug extension"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93048">bug 93048</a>
from <span class="vcard"><a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> <span class="fn">Emil Velikov</span></a>
</span></b>
<pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=93048#c9">comment #9</a>)
<span class="quote">> Emil: can you explain why the cts test still fails on g33?
> This doesn't seem like the kind of test that would be hardware specific.
> </span >
Indeed it's not.
<span class="quote">> g33 wouldn't be in the CI results that you got, because the machine is to
> old/slow to complete in a reasonable time. The test failed on a nightly run.
> </span >
Can you point me out to a PCI ID, so that I can check which path gets executed
on the said platform. I doubt that I'll find such a platform in the wild to do
some actual debugging.
<span class="quote">> /tmp/build_root/m64/bin/cts/glcts
> --deqp-case=ES2-CTS.gtf.GL2ExtensionTests.debug.debug
> dEQP Core GL-CTS-2.0 (0x0052484b) starting..
> target implementation = 'intel-gbm'
>
> Test case 'ES2-CTS.gtf.GL2ExtensionTests.debug.debug'..
> #+ Initial value for GL_DEBUG_GROUP_STACK_DEPTH is 0 but it should be 1</span >
And here comes the strange part... the default (1) stack is allocated via
_mesa_lock_debug_state/debug_create, which gets executed by all khr_debug entry
points (iirc). Thus I'm wondering how it's possible for this to fail.
<span class="quote">> #+ Initial state for GL_DEBUG_OUTPUT is not enabled
> Fail (Fail)
> </span >
While this one is even stranger - as we attempt to set DEBUG_OUTPUT (via the
dri layer), _mesa_set_debug_state_int gets called, which fails to set the flag
only if the _mesa_lock_debug_state/debug_create combo above also fails.
Can you set MESA_DEBUG=1 and LIBGL_DEBUG=verbose and attach (or email) the
output.</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>