With vulkancts 7e3803a, deqp-vk.memory.mapping.random tests were refactored, triggering intermittent failures on all intel platforms. It may be necessary to run vulkancts through piglit with parallel execution to force the errors. Failure output: /tmp/build_root/m64/opt/deqp/modules/vulkan/deqp-vk --deqp-case=dEQP-VK.memory.mapping.random.16 --deqp-log-images=disable --deqp-gl-config-name=rgba8888d24s8 --deqp-surface-width=400 --deqp-surface-height=300 --deqp-visibility=hidden --deqp-surface-type=fbo dEQP Core git-7e3803ae7688f91ac275c2191862fcdc4df6bc72 (0x7e3803ae) starting.. target implementation = 'Default' Test case 'dEQP-VK.memory.mapping.random.16'.. Test case duration in microseconds = 503888 us Fail (Runtime check failed: 'm_reference.read((size_t)(m_range.offset + pos), val)' at vktMemoryMappingTests.cpp:499) DONE! Test run totals: Passed: 0/1 (0.0%) Failed: 1/1 (100.0%) Not supported: 0/1 (0.0%) Warnings: 0/1 (0.0%)
Tested with latest Mesa + Skylake CPU - all memory.mapping.* tests are passing. Test run totals: Passed: 2230/2230 (100.0%) Failed: 0/2230 (0.0%) Not supported: 0/2230 (0.0%) Warnings: 0/2230 (0.0%) Also ran them through piglit with --all-concurrent with the same results.
I'll turn the tests on in CI and see if they are stable over time.
with vulkan-cts-1.1.1, I don't see memory.mapping.random tests in the results anymore. I see memory.mapping.suballocation.random. Have these tests been renamed?
They got renamed in https://github.com/KhronosGroup/VK-GL-CTS/commit/45781a01de0edfb8fb30010512cfa585f16e9824 > Rename tests (added .suballocation subgroups): > * dEQP-VK.memory.mapping.suballocation.* Seems that they are now under suballocation group.
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.