Summary: | [ivb hsw bdw skl kbl cfl] Regressions in deqp and glcts following 9176703788c and b03dcb1e5f5 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Clayton Craft <clayton.a.craft> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Clayton Craft
2018-08-24 15:55:43 UTC
hello Clayton. I ran all these tests on Mesa 18.3.0-develgit-3a9f628, and for me they are passing (for GL46 I made an override before): kernel 4.15.0-30-generic ubuntu 16.04 KBL (630 GT2) All these runs were successful. ./glcts -n dEQP-GLES31.functional.tessellation.state_query.max_uniform_buffer_bindings ./glcts -n dEQP-GLES31.functional.tessellation.state_query.max_combined_texture_image_units ./glcts -n dEQP-GLES31.functional.state_query.integer.max_uniform_buffer_bindings_getinteger64 ./glcts -n dEQP-GLES31.functional.state_query.integer.max_uniform_buffer_bindings_getinteger ./glcts -n dEQP-GLES31.functional.state_query.integer.max_uniform_buffer_bindings_getfloat ./glcts -n dEQP-GLES31.functional.state_query.integer.max_combined_texture_image_units_getinteger64 ./glcts -n dEQP-GLES31.functional.state_query.integer.max_combined_texture_image_units_getinteger ./glcts -n dEQP-GLES31.functional.state_query.integer.max_combined_texture_image_units_getfloat ./glcts -n dEQP-GLES31.functional.compute.basic.ubo_to_ssbo_multiple_groups MESA_GL_VERSION_OVERRIDE=4.6 ./glcts -n KHR-GL46.map_buffer_alignment.functional MESA_GL_VERSION_OVERRIDE=4.6 ./glcts -n KHR-GL46.limits.max_uniform_buffer_bindings Fixed by: 93e8e17fa41 * Revert "mesa: bump GL_MAX_ELEMENTS_INDICES and GL_MAX_ELEMENTS_VERTICES" 9d670fd86cc * Revert recent changes about not including compute in combined limits. |
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.