Bug 31145 - [swrast] glean depthStencil regression
Summary: [swrast] glean depthStencil regression
Status: CLOSED DUPLICATE of bug 31143
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Brian Paul
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-26 19:10 UTC by Vinson Lee
Modified: 2010-10-27 09:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Vinson Lee 2010-10-26 19:10:33 UTC 
mesa: 9b3c4d3e67db9d43fc6b12d2b4943b087c80c926 (master)

Run glean depthStencil. The test now fails but previously passed.

$ glean -r results -t depthStencil --quick
...
Mesa: User error: GL_INVALID_ENUM in glDrawPixels(format or type)
Mesa: User error: GL_INVALID_OPERATION in glDrawPixels(format is not GL_DEPTH_STENCIL_EXT)
Mesa: User error: GL_INVALID_ENUM in glReadPixels(format or type)
Mesa: User error: GL_INVALID_OPERATION in glReadPixels(format is not GL_DEPTH_STENCIL_EXT)
Mesa: User error: GL_INVALID_OPERATION in glCopyTexSubImage2D(source buffer is not integer format)
depthStencilFAIL
	OpenGL Error invalid operation at glCopyTexSubImage2D in testTextureOperations.



326b981d3fafbf0cc253d2b224f0c9ad307038a3 is the first bad commit
commit 326b981d3fafbf0cc253d2b224f0c9ad307038a3
Author: Brian Paul <brianp@vmware.com>
Date:   Mon Oct 25 19:08:55 2010 -0600

    mesa: additional teximage error checks for GL_EXT_texture_integer

:040000 040000 06fba4d6752a438cd33a2c9c40a82608f3b2d632 11b129af3c02ca387fea51812c44d59ad435f90d M	src
bisect run success
Comment 1 Vinson Lee 2010-10-26 19:13:28 UTC 
softpipe also fails glean depthStencil with the same error messages.
Comment 2 Vinson Lee 2010-10-26 19:15:30 UTC 

*** This bug has been marked as a duplicate of bug 31143 ***
Comment 3 Vinson Lee 2010-10-27 09:08:19 UTC 
mesa: 412b9608838b872bc294569b3ee913343a7e66f6 (master)

Verified fixed.

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.