When the ES32-CTS.core and ES31-CTS.core suites were enabled on Intel's Mesa CI, failures in other parts of the test suite were seen on SKL. For example: ES32-CTS.functional.shaders.builtin_functions.common.abs.ivec2_mediump_geometry Failed to set up framebuffer object: glGetError() returned GL_INVALID_OPERATION at glsShaderExecUtil.cpp:638 ES32-CTS.functional.shaders.arrays_of_arrays.return.explicit.mat3_3x4_fragment ShaderCase::execute(): start: glGetError() returned GL_INVALID_OPERATION at glsShaderLibraryCase.cpp:946 ES32-CTS.functional.shaders.multisample_interpolation.interpolate_at_offset.at_sample_position.default_framebuffer glGetError() returned GL_INVALID_OPERATION at es31fMultisampleShaderRenderCase.cpp:475 Running the tests with process isolation removes the errors. These tests are disabled in the CI pending resolution.
These failures only seem to reproduce when tests are running in parallel. The systems in the CI have 8 threads running in parallel. Disabling the following test corrects the failures: ES32-CTS.core.geometry_shader.api.fs_gs_draw_call That test passes, but causes the subsequent failures.
Nanley identified a bug with this test, which we are carrying locally on our CI.
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.