Skip to content
CI

Fix misuse of spec macro in a proposal document #927

Sign in to view logs

Fix misuse of spec macro in a proposal document

Fix misuse of spec macro in a proposal document #927

Triggered via push October 3, 2024 13:41
@oddhackoddhack
pushed d78959a
main
Status Success
Total duration 8m 47s
Artifacts 3

CI.yml

on: push
Build the vulkan specification and generate any associated files (such as vulkan.h)
6m 53s
Build the vulkan specification and generate any associated files (such as vulkan.h)
Verify repository license compliance
39s
Verify repository license compliance
Run various checker scripts on the spec and XML sources
50s
Run various checker scripts on the spec and XML sources
Build a test spec and check against expectation, to make sure the spec toolchain works as expected
1m 21s
Build a test spec and check against expectation, to make sure the spec toolchain works as expected
Build the core-only spec, to try and catch ifdef errors in extension markup
51s
Build the core-only spec, to try and catch ifdef errors in extension markup
Run Vulkan CTS framework tests to validate against XML changes
1m 59s
Run Vulkan CTS framework tests to validate against XML changes
Generate Rust bindings (Ash crate)
56s
Generate Rust bindings (Ash crate)
Generate the vulkan C++ header (vulkan.hpp)
1m 9s
Generate the vulkan C++ header (vulkan.hpp)
Compile a simple test program that uses vulkan.h
14s
Compile a simple test program that uses vulkan.h
Build-test Rust bindings (Ash crate)
27s
Build-test Rust bindings (Ash crate)
Compile a simple test program that uses vulkan.hpp
18s
Compile a simple test program that uses vulkan.hpp
Fit to window
Zoom out
Zoom in

Artifacts

Produced during runtime
Name Size
ash-outputs Expired
1.16 MB
hpp-outputs Expired
1.63 MB
spec-outputs Expired
42.9 MB