regressed by mesa 4ec1c2bb7f4ed4238ce80e25f93dd1120201aaec mesa: remove OES_shader_io_blocks enable This extension should just be available whenever ES 3.1 is available. With the new extension verification infrastructure, it will only be enable-able on a #version 310 es shader, rendering the original reason for having a separate enable moot. deqp-gles31 --deqp-case=dEQP-GLES31.functional.separate_shader.validation.io_blocks.match_different_member_struct_names --deqp-log-images=disable --deqp-gl-config-name=rgba8888d24s8 --deqp-surface-width=400 --deqp-surface-height=300 --deqp-visibility=hidden dEQP Core git-2941552f8fb43d1612b601979d27131bb51e4f09 (0x2941552f) starting.. target implementation = 'X11 GLX' Test case 'dEQP-GLES31.functional.separate_shader.validation.io_blocks.match_different_member_struct_names'.. Vertex shader compile time = 3.151000 ms Link time = 0.580000 ms Fragment shader compile time = 0.317000 ms Link time = 0.639000 ms Test case duration in microseconds = 8299 us Fail (draw: glGetError() returned GL_INVALID_OPERATION at glsShaderLibraryCase.cpp:1025) DONE! Test run totals: Passed: 0/1 (0.0%) Failed: 1/1 (100.0%) Not supported: 0/1 (0.0%) Warnings: 0/1 (0.0%)
Created attachment 126113 [details] attachment-5753-0.html Just a guess - my commit effectively enabled the ext on those two platforms. This test was previously skipping. Also this test currently fails on the other platforms as well. Please let me know if any of those guesses are wrong. If those are right, then it's expected that this test would fail on those platforms. (Hsw recently gained es 3.1, but the enablement forgot to flip the ext in question on. I removed the separate enable, effectively flipping it on for hsw.)
Thanks for pointing me in the right direction. You are right, the test fails on other platforms, due to: https://www.khronos.org/bugzilla/show_bug.cgi?id=1500
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.