Current mustpass is checked into repository and can be found at:
- external/vulkancts/mustpass/1.1.0/vk-default.txt
+ external/vulkancts/mustpass/1.1.1/vk-default.txt
Vulkan CTS mustpass can be re-generated by running:
Following command line options MUST be used when running CTS:
- --deqp-caselist-file=<vulkancts>/external/vulkancts/mustpass/1.1.0/vk-default.txt
+ --deqp-caselist-file=<vulkancts>/external/vulkancts/mustpass/1.1.1/vk-default.txt
--deqp-log-images=disable
--deqp-log-shader-sources=disable
### Android
- adb push <vulkancts>/external/vulkancts/mustpass/1.1.0/vk-default.txt /sdcard/vk-default.txt
+ adb push <vulkancts>/external/vulkancts/mustpass/1.1.1/vk-default.txt /sdcard/vk-default.txt
adb shell
In device shell:
If the submission package covers multiple products, you can list them by appending
additional `PRODUCT:` lines to the conformance statement. For example:
- CONFORM_VERSION: vulkan-cts-1.1.0.0
+ CONFORM_VERSION: vulkan-cts-1.1.1.0
PRODUCT: Product A
PRODUCT: Product B
...
script. The script takes two arguments: path to extracted submission package
and path to current mustpass list. For example:
- python external/vulkancts/scripts/verify_submission.py VK_11_Khronos_1/ external/vulkancts/mustpass/1.1.0/vk-default.txt
+ python external/vulkancts/scripts/verify_submission.py VK_11_Khronos_1/ external/vulkancts/mustpass/1.1.1/vk-default.txt
Please note that the script reports a warning even for a correctly generated git-log.txt
If your git-log.txt contains only head commit of the release tag then