[Piglit] [PATCH 2/2] arb_robustness: test with and without PBO

Brian Paul brianp at vmware.com
Mon May 7 08:40:34 PDT 2012


On 05/07/2012 09:28 AM, nobled wrote:
> On Wed, May 2, 2012 at 3:18 PM, Brian Paul<brianp at vmware.com>  wrote:
>> On 05/02/2012 10:41 AM, nobled wrote:
>>>
>>> On Wed, May 2, 2012 at 11:20 AM, Brian Paul<brianp at vmware.com>    wrote:
>>>>
>>>> On 05/01/2012 05:01 PM, nobled wrote:
>>>>>
>>>>>
>>>>> ---
>>>>>   tests/spec/arb_robustness/client-mem-bounds.c |  147
>>>>> +++++++++++++++++--------
>>>>>   1 files changed, 103 insertions(+), 44 deletions(-)
>>>>
>>>>
>>>>
>>>> Hmmm, this patch doesn't apply cleanly for me:
>>>
>>> Can you try the 'robust' branch from here?
>>> https://github.com/nobled/piglit.git
>>
>>
>> Fails w/ NVIDIA:
>>
>> $ bin/arb_robustness_client-mem-bounds -auto
>> Unexpected GL error: GL_INVALID_OPERATION 0x502
>> (Error at
>> /home/brian/projects/piglit-nobled/piglit/tests/spec/arb_robustness/client-mem-bounds.c:57)
>> (PIXEL_PACK_BUFFER=1, bufSize = -2147483520, expected 128 bytes to be
>> required)
>> PIGLIT: {'result': 'fail' }
> That seems wrong. The spec says stuff like
>
>       "When calling
>        GetnPixelMap{ui us f}vARB, if a pixel pack buffer object is bound
>        and<n>  is greater than<bufSize>, but<data>+<n>  does not exceed
>        the size of the buffer, no error results."
>
> and similar for the other entrypoints. And the PBO should be big
> enough, since it's passing on Mesa for me. Can you pull the branch
> again and see which call is failing?


$ bin/arb_robustness_client-mem-bounds -auto
Unexpected GL error: GL_INVALID_OPERATION 0x502
(Error at 
/home/brian/projects/piglit-nobled/piglit/tests/spec/arb_robustness/client-mem-bounds.c:59)
glGetnPixelMap*vARB(PIXEL_PACK_BUFFER=1, bufSize = -2147483520, 
expected 128 bytes to be required)
PIGLIT: {'result': 'fail' }


-Brian


More information about the Piglit mailing list