Skip to content

ci: Move Vulkan CTS patches to their own directory

This is related with the effort to automate uprev_vulkancts_in_mesa that has a first drafted approach in gfx-ci/ci-uprev!61. I would like to open a discussion about the minimal changes that could help on this task. This MR can change a lot before ready to be merged.

It has been initially split in to commits:

  • Review how the patches needed for VulkanCTS are managed to use the patch subdirectory as skqp does. Also, encapsulate the VulkanCTS revision in a variable like how piglit build references the revision.
  • The jobs related to the build of deqp may fail when patches to VulkanCTS cannot be applied. This is a feature to verify they are required, but they can block an update of the revision to know if they aren't further needed.

The review process has transformed this MR to single commit with changes focused in relocate the patches to the existing directory for this purpose and resemble the two sources of patches for VulkanCTS to look similar. ci-uprev will take from here the information to check if a patch can be applied while upreving as well as it will provide a way to intoduce new patches.

Edited by Sergi Blanch Torné

Merge request reports