<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - i965: Timeout in dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer.5" href="https://bugs.freedesktop.org/show_bug.cgi?id=104271#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - i965: Timeout in dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer.5" href="https://bugs.freedesktop.org/show_bug.cgi?id=104271">bug 104271</a> from <a class="email" href="mailto:currojerez@riseup.net" title="Francisco Jerez <currojerez@riseup.net>"> Francisco Jerez</a> <pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=104271#c6">comment #6</a>) > On BSW, the run-time of this test goes from 39s to 175s, on the bisected > commit. We need to improve performance by >25% beyond just fixing Curro's > regression. > There's a good chance that the fix I'm working on will bring us below the 30s bar, but it's hard to predict with certainty since there may be other passes behaving inefficiently in this test-case. > As per Chad's comment, this performance is bad enough that it will prevent > us from passing the android CTS. > > It may not be a *Khronos* conformance issue, but it is a conformance issue > nonetheless, for all of our platforms. Except that to the extent that the CTS doesn't match the specification we are more likely to be talking about a conformance problem of the CTS rather than of our implementation...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>