<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [REGRESSION] [BISECTED] [GLESCTS] race between destruction of types and shader compilation (?)" href="https://bugs.freedesktop.org/show_bug.cgi?id=110796#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [REGRESSION] [BISECTED] [GLESCTS] race between destruction of types and shader compilation (?)" href="https://bugs.freedesktop.org/show_bug.cgi?id=110796">bug 110796</a> from <a class="email" href="mailto:agomez@igalia.com" title="Andrés Gómez García <agomez@igalia.com>"> Andrés Gómez García</a> <pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=110796#c10">comment #10</a>) > In my opinion, this should have blocked the 19.1 release. I think you are right. > I'm altering the title to make it clear that this prevents i965 from being > compliant with the gles cts. Thanks! > The bug originator is unlikely to remember that the bug is unfixed and add > it to the release tracker. The release manager may search in bugzilla for > unfixed bugs affecting the release, but will find a lot of noise in the > results. Unfortunately, at the time of reporting it was unclear to me whether this was a regression of just a problem happening in a very specific condition. Notice that I was not using master directly but a patched master :(</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>