Bug 89329 - glsl-deriv-varyings regression
Summary: glsl-deriv-varyings regression
Status: RESOLVED DUPLICATE of bug 87407
Alias: None
Product: piglit
Classification: Unclassified
Component: tests (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Piglit Mailing List
QA Contact: Piglit Mailing List
URL:
Whiteboard:
Keywords: bisected, regression
Depends on:
Blocks:
 
Reported: 2015-02-26 02:07 UTC by Vinson Lee
Modified: 2015-03-02 05:59 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Vinson Lee 2015-02-26 02:07:32 UTC 
piglit: 10d692dfbe0d1cab7c63116169402f2862e2c869 (master)

$ ./bin/glsl-deriv-varyings  -auto
Probe color at (355,125)
  Expected: 0.800000 0.400000 0.000000
  Observed: 0.800000 0.000000 0.000000
PIGLIT: {"result": "fail" }


cd62eff8e5925efa56778d7a103402e96d19a794 is the first bad commit
commit cd62eff8e5925efa56778d7a103402e96d19a794
Author: Andres Gomez <agomez@igalia.com>
Date:   Tue Dec 16 18:01:42 2014 +0100

    glsl-deriv-varyings: Fix some typos
    
    1. Compile the correct shaders for fs4 and fs5.
    
    2. Add a missing ) in fragShaderText5.
    
    Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>

:040000 040000 b53d55bd3a7d6fadefafc71bf56e91705471e1bf 179471cdc12d9c055c3a23961e0176296292fe63 M	tests
bisect run success
Comment 1 Ian Romanick 2015-02-26 02:11:00 UTC 
I believe we know the cause of the problem, but I don't know whether or not Andrés is fixing it...

*** This bug has been marked as a duplicate of bug 87407 ***
Comment 2 Andrés Gómez García 2015-02-26 08:40:37 UTC 
(In reply to Ian Romanick from comment #1)
> I believe we know the cause of the problem, but I don't know whether or not
> Andrés is fixing it...
> 
> *** This bug has been marked as a duplicate of bug 87407 ***

Yes, I only have to find the time. Hopefully during this weekend ...
Comment 3 lu hua 2015-03-02 05:59:27 UTC 
I also see this fail on all platforms.

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.