Bug 60524

Summary: [softpipe] piglit depthstencil-render-miplevels 146 s=z24_s8 regression
Product: Mesa Reporter: Vinson Lee <vlee>
Component: OtherAssignee: mesa-dev
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: maraeo
Version: gitKeywords: regression
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Vinson Lee 2013-02-09 01:05:27 UTC
mesa: 1d71106f5c7084c90dacc8af7d06fa8c8eb6d9f1 (master)

$ ./bin/depthstencil-render-miplevels 146 s=z24_s8 -auto
Mesa warning: failed to remap glClampColorARB
Mesa warning: failed to remap glTexBufferARB
Mesa warning: failed to remap glFramebufferTextureARB
Mesa warning: failed to remap glVertexAttribDivisorARB
Mesa warning: failed to remap glProgramParameteriARB
Probing miplevel 0 stencil
Probe at (0, 0)
  Expected: 1
  Observed: 0
Probing miplevel 1 stencil
Probe at (0, 0)
  Expected: 2
  Observed: 0
Probing miplevel 2 stencil
Probe at (0, 0)
  Expected: 3
  Observed: 0
Probing miplevel 3 stencil
Probe at (0, 0)
  Expected: 4
  Observed: 0
Probing miplevel 4 stencil
Probe at (0, 0)
  Expected: 5
  Observed: 0
Probing miplevel 5 stencil
Probe at (0, 0)
  Expected: 6
  Observed: 0
Probing miplevel 6 stencil
Probe at (0, 0)
  Expected: 7
  Observed: 0
Probing miplevel 7 stencil
Probe at (0, 0)
  Expected: 8
  Observed: 0
PIGLIT: {'result': 'fail' }

16a30e201e10278049b6464d21556f59d892ecf0 is the first bad commit
commit 16a30e201e10278049b6464d21556f59d892ecf0
Author: Marek Olšák <maraeo@gmail.com>
Date:   Mon Jan 14 06:45:50 2013 +0100

    softpipe: implement separate depth-stencil clear
    
    The CAP is going away.
    
    Reviewed-by: Brian Paul <brianp@vmware.com>

:040000 040000 3776550e80223b032167572d7d34e8dc4b64a31d dcfc8a78bba351a39a856c95d9ad3cf64021f552 M	src
bisect run success
Comment 1 Brian Paul 2013-02-12 15:15:30 UTC
Fixed by commit 4bfdef87e66bfb2459af570351798d7754ddfb9f

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.