Bug 91112 - [HSW/BYT] dEQP-GLES3.functional.uniform_api.random.23 test timeout
Summary: [HSW/BYT] dEQP-GLES3.functional.uniform_api.random.23 test timeout
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 10.6
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-25 21:19 UTC by Brian Wilson
Modified: 2016-11-03 00:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Brian Wilson 2015-06-25 21:19:18 UTC
This isn't an outright test failure per-se, but dEQP is marking the test timeout as such.

Timeout is on: dEQP-GLES3.functional.uniform_api.random.23

Mesa commit being tested:
c2a0600d5b0645533ba442b5ab879b23c2564a4d: "i965: Don't set NirOptions for stages that will use the vec4 backend."
Plus patches:
- 10.6-i965-do-not-round-line-width-when-multisampling-or-a.patch
- 10.6-mesa-add-GL_RED-GL_RG-support-for-floating-point-tex.patch
- 10.6-i965-Momentarily-pretend-to-support-ARB_texture_sten.patch
- 10.6-Revert-i965-Advertise-a-line-width-of-40.0-on-Cherry.patch

This test passes on BDW and BSW, and passed on HSW/BYT with an older Mesa commit (November 18, 2014: 129178893b2260df22db96327c5ca9c2ce7db046 "glsl: Generate unique names for each const array lowered to uniforms" + ~10 patches)
Comment 1 Matt Turner 2015-08-23 04:02:19 UTC
Please assign i965 bugs to Component: Drivers/DRI/i965.
Comment 2 Iago Toral 2015-09-15 08:57:05 UTC
The test takes a while to finish, around 12 seconds for me, but it finishes and is marked as "Passed" for me every time (5/5), at least if I run it standalone.
Comment 3 Matt Turner 2016-11-03 00:44:04 UTC
This test passes in 1.2 seconds on HSW for me. Please reopen if you think there's still a problem.


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.