<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - dEQP-GLES3.functional.shaders.derivate.dfdx.fbo_float_vec2_highp fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=97002#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - dEQP-GLES3.functional.shaders.derivate.dfdx.fbo_float_vec2_highp fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=97002">bug 97002</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>I agree with Mark. I don't think we can pass these. It looks like they were removed from the mustpass list in: commit ea026b329e6bf73f109cda914c90f08d5f7a5b8d Author: Pyry Haulos <<a href="mailto:phaulos@google.com">phaulos@google.com</a>> Date: Tue Jul 21 15:12:53 2015 -0700 Remove highp float FBO dfd*() tests from mustpass Bug: 22628471 Bug: 22632003 Change-Id: Ia9d2b9a5e04ad317cbcc8782c9efaeedd94a0a58 Sadly, the commit messages offer no explanation as to why, and I believe those bug IDs are for a Google-internal bug tracker. (I suppose we could ask Pyry.) Having looked around for documentation that could explain the problems, I found <a href="https://hsdes.intel.com/appstore/article/#/1208680029/main">https://hsdes.intel.com/appstore/article/#/1208680029/main</a> which indicates that the Intel Android team isn't planning on fixing these tests either. I found another HSD somewhere which suggested this comes down to numerical imprecision when interpolating inputs, and that testing dFdx is hard. I'm guessing that Skylake must have gotten a little better in that regard; these tests fail on both Broadwell and Haswell, despite us using the exact same code. So I don't think we can fix this. Someone will probably want to follow up with the WebGL conformance developers and Google developers and remove tests ported from blacklisted dEQP tests. Sorry :(</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>