<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#c11">Comment # 11</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:jasuarez@igalia.com" title="Juan A. Suarez <jasuarez@igalia.com>"> Juan A. Suarez</a> <pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=110796#c10">comment #10</a>) > > > Juan, do you have any suggestions for how we can catch these bugs in the > release process? I would suggest relying on the "bisected, regression" > keywords, but this list seems too long for me: > > <a href="https://bugs.freedesktop.org/buglist">https://bugs.freedesktop.org/buglist</a>. > cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&keywords=bisected% > 2C%20regression%2C%20&keywords_type=allwords&list_id=676302&order=bug_id%20DE > SC&product=Mesa&query_format=advanced > Maybe we can short the list if we search for all the bugs created since the latest branch point (for 19.1, they would be all the tests created after 19.0 branchpoint). The rationale is that all the previous bugs didn't block 19.0, so they shouldn't block 19.1.</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>