Bug 99039 - [dEQP, EGL] dEQP-EGL.functional.color_clears.multi_context tests crash
Summary: [dEQP, EGL] dEQP-EGL.functional.color_clears.multi_context tests crash
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Tapani Pälli
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 98315
  Show dependency treegraph
 
Reported: 2016-12-09 22:26 UTC by Mark Janes
Modified: 2016-12-14 01:26 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Mark Janes 2016-12-09 22:26:25 UTC
Several tests crash in this category, for example:

dEQP-EGL.functional.color_clears.single_context.gles1.rgb888_pbuffer
Comment 1 Tapani Pälli 2016-12-12 09:09:07 UTC
(In reply to Mark Janes from comment #0)
> Several tests crash in this category, for example:
> 
> dEQP-EGL.functional.color_clears.single_context.gles1.rgb888_pbuffer

Are all of those GLES1 tests? For me this test prints out following:

InternalError (Test case requires client API not supported in current build at teglRenderCase.cpp:109)

I'm not sure how to setup dEQP build to support GLES1, I'll take a look at why it does not happen.
Comment 2 Tapani Pälli 2016-12-12 09:31:57 UTC
these are the ones that fail for me with 'InternalError' (related to dEQP not build with GLES1 support):

--- 8< ---
dEQP-EGL.functional.color_clears.single_context.gles1.rgb888_window
dEQP-EGL.functional.color_clears.single_context.gles1.rgb888_pbuffer
dEQP-EGL.functional.color_clears.single_context.gles1.rgba8888_window
dEQP-EGL.functional.color_clears.single_context.gles1.rgba8888_pbuffer
dEQP-EGL.functional.color_clears.multi_context.gles1.rgb888_window
dEQP-EGL.functional.color_clears.multi_context.gles1.rgb888_pbuffer
dEQP-EGL.functional.color_clears.multi_context.gles1.rgba8888_window
dEQP-EGL.functional.color_clears.multi_context.gles1.rgba8888_pbuffer
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2.rgb888_window
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2.rgb888_pbuffer
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2.rgba8888_window
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2.rgba8888_pbuffer
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2_gles3.rgb888_window
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2_gles3.rgb888_pbuffer
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2_gles3.rgba8888_window
dEQP-EGL.functional.color_clears.multi_context.gles1_gles2_gles3.rgba8888_pbuffer
dEQP-EGL.functional.color_clears.multi_thread.gles1.rgb888_window
dEQP-EGL.functional.color_clears.multi_thread.gles1.rgb888_pbuffer
dEQP-EGL.functional.color_clears.multi_thread.gles1.rgba8888_window
dEQP-EGL.functional.color_clears.multi_thread.gles1.rgba8888_pbuffer
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2.rgb888_window
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2.rgb888_pbuffer
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2.rgba8888_window
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2.rgba8888_pbuffer
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2_gles3.rgb888_window
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2_gles3.rgb888_pbuffer
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2_gles3.rgba8888_window
dEQP-EGL.functional.color_clears.multi_thread.gles1_gles2_gles3.rgba8888_pbuffer
Comment 3 Tapani Pälli 2016-12-12 13:03:31 UTC
I patched dEQP build to work with gles1 (required setting DEQP_SUPPORT_GLES1, DEQP_GLES1_LIBRARIES + setting manually include dir via CXXFLAGS) and got following results:

Running with --deqp-case=dEQP-EGL.functional.color_clears*

(against Mesa ec0a0a60cc2773624f6c72b11c4d37519397a59d)

Test run totals:
  Passed:        52/384 (13.5%)
  Failed:        0/384 (0.0%)
  Not supported: 332/384 (86.5%)
  Warnings:      0/384 (0.0%)

same result both on Haswell and Skylake.


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.