Bug 65874 - piglit ext_transform_feedback-intervening-read output regression
Summary: piglit ext_transform_feedback-intervening-read output regression
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-06-18 00:18 UTC by Vinson Lee
Modified: 2013-07-04 20:38 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2013-06-18 00:18:04 UTC
mesa: eb2021507556633cd6ba64cda26653e3c43e80df (master)

$ ./bin/ext_transform_feedback-intervening-read output -auto
Read incorrect data for vertex 0.
Readback: position=(0.000000, -1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Expected: position=(-1.000000, -1.000000, 0.000000, 1.000000), color=(1.000000, 1.000000, 0.000000, 1.000000)
Read incorrect data for vertex 1.
Readback: position=(1.000000, -1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Expected: position=(0.000000, -1.000000, 0.000000, 1.000000), color=(1.000000, 1.000000, 0.000000, 1.000000)
Read incorrect data for vertex 2.
Readback: position=(0.000000, 1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Expected: position=(-1.000000, 1.000000, 0.000000, 1.000000), color=(1.000000, 1.000000, 0.000000, 1.000000)
Read incorrect data for vertex 3.
Readback: position=(0.000000, 1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Expected: position=(-1.000000, 1.000000, 0.000000, 1.000000), color=(1.000000, 1.000000, 0.000000, 1.000000)
Read incorrect data for vertex 4.
Readback: position=(1.000000, -1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Expected: position=(0.000000, -1.000000, 0.000000, 1.000000), color=(1.000000, 1.000000, 0.000000, 1.000000)
Read incorrect data for vertex 5.
Readback: position=(1.000000, 1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Expected: position=(0.000000, 1.000000, 0.000000, 1.000000), color=(1.000000, 1.000000, 0.000000, 1.000000)
Read incorrect data for vertex 6.
Readback: position=(12345.000000, 12345.000000, 12345.000000, 12345.000000), color=(12345.000000, 12345.000000, 12345.000000, 12345.000000)
Expected: position=(0.000000, -1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Read incorrect data for vertex 7.
Readback: position=(12345.000000, 12345.000000, 12345.000000, 12345.000000), color=(12345.000000, 12345.000000, 12345.000000, 12345.000000)
Expected: position=(1.000000, -1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
Read incorrect data for vertex 8.
Readback: position=(12345.000000, 12345.000000, 12345.000000, 12345.000000), color=(12345.000000, 12345.000000, 12345.000000, 12345.000000)
Expected: position=(0.000000, 1.000000, 0.000000, 1.000000), color=(0.000000, 0.000000, 1.000000, 1.000000)
PIGLIT: {'result': 'fail' }

41966fdb3b71c0b70aeb095e0eb3c5626c144a3a is the first bad commit
commit 41966fdb3b71c0b70aeb095e0eb3c5626c144a3a
Author: Zack Rusin <zackr@vmware.com>
Date:   Thu Jun 13 17:57:47 2013 -0400

    draw: clear the draw buffers in draw
    
    Moves clearing of the draw so target buffers to the draw
    module. They had to be cleared in the drivers before
    which was quite messy.
    
    Signed-off-by: Zack Rusin <zackr@vmware.com>
    Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
    Reviewed-by: Brian Paul <brianp@vmware.com>

:040000 040000 c836c139da6f4f91be2b86bc65f9e1ccc3bc3e14 1de6a5310e52318edaba24ceba214c29c2e78e6a M	src
bisect run success
Comment 1 Vinson Lee 2013-07-04 20:38:55 UTC
mesa: f3bbf65929e395360e5565d08d015977dd5b79fa (master)

piglit ext_transform_feedback-intervening-read output now passes on latest master.


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.