4 This document describes how to build and run Vulkan Conformance Test suite.
6 Vulkan CTS is built on dEQP framework. dEQP documentation is available
7 at http://source.android.com/devices/graphics/testing.html
14 * Git (for checking out sources)
15 * Python 2.7.x (all recent versions in 2.x should work, 3.x is not supported)
19 * Visual Studio 2013 or newer (glslang uses several C++11 features)
22 * Standard toolchain (make, gcc/clang)
26 * Android SDK with following packages:
32 * Windows: either NMake or JOM in PATH
38 To build dEQP, you need first to download sources for zlib, libpng, glslang,
41 To download sources, run:
43 $ python external/fetch_sources.py
45 You may need to re-run fetch_sources.py to update to the latest glslang and
46 spirv-tools revisions occasionally.
48 NOTE: glslang integration is not yet available on Android due to a toolchain
49 bug, so pre-compiled SPIR-V binaries must be used. See instructions below.
51 With CMake out-of-source builds are always recommended. Create a build directory
52 of your choosing, and in that directory generate Makefiles or IDE project
58 > cmake <path to vulkancts> -G"Visual Studio 12"
59 > start dEQP-Core-default.sln
64 > cmake <path to vulkancts> -G"Visual Studio 12 Win64"
65 > start dEQP-Core-default.sln
70 $ cmake <path to vulkancts> -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_FLAGS=-m32 -DCMAKE_CXX_FLAGS=-m32
73 Release build can be done by using -DCMAKE_BUILD_TYPE=Release
78 $ cmake <path to vulkancts> -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_FLAGS=-m64 -DCMAKE_CXX_FLAGS=-m64
84 $ python android/scripts/build.py
85 $ python android/scripts/install.py
91 Current mustpass is checked into repository and can be found at:
93 external/vulkancts/mustpass/1.0.0/vk-default.txt
95 Vulkan CTS mustpass can be re-generated by running:
97 $ python <vulkancts>/external/vulkancts/build_mustpass.py
100 Pre-compiling SPIR-V binaries
101 -----------------------------
103 For distribution, and platforms that don't support GLSL to SPIR-V compilation,
104 SPIR-V binaries must be pre-built with following command:
106 $ python external/vulkancts/build_spirv_binaries.py
108 Binaries will be written to external/vulkancts/data/vulkan/prebuilt/.
110 Test modules (or in case of Android, the APK) must be re-built after building
111 SPIR-V programs in order for the binaries to be available.
117 Following command line options MUST be used when running CTS:
119 --deqp-caselist-file=<vulkancts>/external/vulkancts/mustpass/1.0.0/vk-default.txt
120 --deqp-log-images=disable
121 --deqp-log-shader-sources=disable
123 In addition on multi-device systems the device for which conformance is claimed
124 can be selected with:
126 --deqp-vk-device-id=<value>
128 No other command line options are allowed.
133 > cd <builddir>/external/vulkancts/modules/vulkan
134 > Debug/deqp-vk.exe --deqp-caselist-file=...
136 Test log will be written into TestResults.qpa
141 $ cd <builddir>/external/vulkancts/modules/vulkan
142 $ ./deqp-vk --deqp-vk-caselist-file=...
147 $ adb push <vulkancts>/external/vulkancts/mustpass/1.0.0/vk-default.txt /sdcard/vk-default.txt
152 $ am start -n com.drawelements.deqp/android.app.NativeActivity -e cmdLine "deqp --deqp-caselist-file=/sdcard/vk-default.txt --deqp-log-images=disable --deqp-log-shader-sources=disable --deqp-log-filename=/sdcard/TestResults.qpa"
154 Process can be followed by running:
158 Test log will be written into /sdcard/TestResults.qpa
161 Conformance Submission Package Requirements
162 -------------------------------------------
164 Conformance submission package must contain following:
166 1) Full test logs (TestResults.qpa) from CTS runs against all driver builds
167 2) Result of "git status" and "git log" from CTS source directory
168 3) Any patches used on top of release tag
169 4) Conformance statement
171 Test logs (1) should be named TestResults-<driver build type>.qpa, for example
172 TestResults-armeabi-v7a.qpa. On platforms where multiple different driver
173 builds (for example 64-bit and 32-bit) are present, CTS must be ran against
176 CTS build must always be done from clean git repository that doesn't have any
177 uncommitted changes. Thus it is necessary to run and capture output of "git
178 status" and "git log" (2) in the source directory:
180 git status > <submission pkg dir>/git-status.txt
181 git log <release tag>..HEAD > <submission pkg dir>/git-log.txt
183 Any changes made to CTS must be committed to the repository, and provided
184 as part of the submission package (3). This can be done by running:
186 git format-patch -o <submission pkg dir> <release tag>..HEAD
188 In general bugfixes and changes to platform-specific code (mostly under
189 framework/platform) are allowed.
191 Conformance statement (4) must be included in a file called STATEMENT-<adopter>
192 and must contain following:
194 CONFORM_VERSION: <git tag of CTS release>
195 PRODUCT: <string-value>
199 Note that product/cpu/os information is also captured in dEQP-VK.info.* tests
200 if vk::Platform::describePlatform() is implemented.
206 Vulkan support from Platform implementation requires providing
207 getVulkanPlatform() method in tcu::Platform class implementation.
209 See framework/common/tcuPlatform.hpp and examples in
210 framework/platform/win32/tcuWin32Platform.cpp and
211 framework/platform/android/tcuAndroidPlatform.cpp.
217 For testing and development purposes it might be useful to be able to run
218 tests on dummy Vulkan implementation. One such implementation is provided in
219 vkNullDriver.cpp. To use that, implement vk::Platform::createLibrary() with
220 vk::createNullDriver().
226 Vulkan test module can be used with Cherry (GUI for test execution and
227 analysis). Cherry is available at
228 https://android.googlesource.com/platform/external/cherry. Please follow
229 instructions in README to get started.
231 To enable support for Vulkan tests, dEQP-VK module must be added to list of
234 In cherry/testrunner.go, add following line to testPackageDescriptors list
235 (line 608 in NewTestRunner function):
237 {"dEQP-VK", "deqp-vk", "../external/vulkancts/modules/vulkan", dataDir + "dEQP-VK-cases.xml"},
239 Before first launch, and every time test hierarchy has been modified, test
240 case list must be refreshed by running:
242 $ python scripts/build_caselists.py path/to/cherry/data
244 Cherry must be restarted for the case list update to take effect.