search

KhronosGroup / VK-GL-CTS

Khronos Vulkan, OpenGL, and OpenGL ES Conformance Tests
https://www.khronos.org/
Apache License 2.0
521 stars 290 forks source link

dEQP-VK.pipeline.monolithic.bind_buffers_2.separate.stride_40_28_offset_0_0.count_3 , is this test working? #425

Open gmmo opened 10 months ago

gmmo commented 10 months ago

Hi, I am running this test in two complete different drivers (Windows and Android) and I am getting the exact same failure.

This makes me very suspicious of the test itself has a bug?

I ran on Windows as below (Radeon AMD intergrated)

.\deqp-vk.exe --deqp-case=dEQP-VK.pipeline.monolithic.bind_buffers_2.separate.stride_40_28_offset_0_0.count_3 --deqp-log-filename=stride_40_28_offset_0_0.qpa

and here on Android (Samsung Device)

adb shell "am start -n com.drawelements.deqp/android.app.NativeActivity -e cmdLine 'deqp --deqp-case=dEQP-VK.pipeline.monolithic.bind_buffers_2.separate.stride_40_28_offset_0_0.count_3 --deqp-log-filename=/sdcard/vk_cts/stride_40_28_offset_0_0.qpa'"

both produce the same failures.

#sessionInfo releaseName vulkan-cts-1.3.7.1-100-g596cf9896cc7d5d05bb1523d5bc38a3b32de4e3b
#sessionInfo releaseId 0x596cf989
#sessionInfo targetName "Default"
#sessionInfo vendorID 0x1002
#sessionInfo deviceID 0x1681
#sessionInfo deviceName AMD Radeon(TM) Graphics
#sessionInfo commandLineParameters "--deqp-case=dEQP-VK.pipeline.monolithic.bind_buffers_2.separate.stride_40_28_offset_0_0.count_3 --deqp-log-filename=stride_40_28_offset_0_0.qpa"

a bunch of stuff

 <Text>vkCmdBindVertexBuffers2</Text>
 <Text>binding 0, buffer 0xcad092000000000d, offset 0, size 280, stride a0</Text>
 <Text>binding 1, buffer 0xe7e6d0000000000f, offset 0, size 1c0, stride 70</Text>
 <Text>binding 2, buffer 0xcad092000000000d, offset 8, size 278, stride a0</Text>
 <Text>binding 3, buffer 0xe7e6d0000000000f, offset 8, size 1b8, stride 70</Text>
 <Text>binding 4, buffer 0xcad092000000000d, offset c, size 274, stride a0</Text>
 <Text>binding 5, buffer 0xe7e6d0000000000f, offset c, size 1b4, stride 70</Text>
 <Text>Color at (0, 0) was (0.24, 0.44, 0, 0), but expected color was (0.24, 0.44, 0.64, 0.84)</Text>
 <Number Name="TestDuration" Description="Test case duration in microseconds" Tag="Time" Unit="us">467162</Number>
 <Result StatusCode="Fail">Fail</Result>
</TestCaseResult>

#endTestCaseResult

Run took 5.32 seconds

#endSession

Android Results (complete different manufacture and driver

#sessionInfo releaseName vulkan-cts-1.3.7.0-129-g4340e6e70bc62746e7cd03e8d03541e446f4f17f
#sessionInfo releaseId 0x4340e6e7
#sessionInfo targetName "Android"
#sessionInfo commandLineParameters "deqp --deqp-case=dEQP-VK.pipeline.monolithic.bind_buffers_2.separate.stride_40_28_offset_0_0.count_3 --deqp-log-filename=/sdcard/vk_cts/stride_40_28_offset_0_0.qpa"

#beginSession
.... a bunch of stuff

 <Text>vkCmdBindVertexBuffers2</Text>
 <Text>binding 0, buffer 0x00000076ddc7f080, offset 0, size 280, stride a0</Text>
 <Text>binding 1, buffer 0x00000076ddc7eae0, offset 0, size 1c0, stride 70</Text>
 <Text>binding 2, buffer 0x00000076ddc7f080, offset 8, size 278, stride a0</Text>
 <Text>binding 3, buffer 0x00000076ddc7eae0, offset 8, size 1b8, stride 70</Text>
 <Text>binding 4, buffer 0x00000076ddc7f080, offset c, size 274, stride a0</Text>
 <Text>binding 5, buffer 0x00000076ddc7eae0, offset c, size 1b4, stride 70</Text>
 <Text>Color at (0, 0) was (0.24, 0.44, 0, 0), D but expected color was (0.24, 0.44, 0.64, 0.84)</Text>
 <Number Name="TestDuration" Description="Test case duration in microseconds" Tag="Time" Unit="us">506308</Number>
 <Result StatusCode="Fail">Fail</Result>
</TestCaseResult>

#endTestCaseResult
AlexGalazin-IMG commented 10 months ago

We don't have any issues raised against this test. I suggest you check with the Vulkan driver implementations in question