Drop deqp-vksc from vulkan-cts package and upgrade vulkan-cts: 1.3.10.0 -> 1.4.1.3

[jljusten]

Vulkan SC (Safety Critical) CTS is separate from the Vulkan CTS. This change splits it out into a separate vulkansc-cts package, and uses the latest Vulkan SC CTS tag, vulkansc-cts-1.0.2.1 with this package.

Then, the Vulkan CTS is upgraded: 1.3.10.0 -> 1.4.1.2.

These changes were prompted by the Vulkan SC executable (deqp-vksc) failing to build with the newer Vulkan CTS version. This build failure is not a bug of the CTS as the vulkan-cts-* tags are for the Vulkan CTS and not the Vulkan SC CTS. In other words, vulkan-cts-* tags support the Vulkan CTS and vulcansc-cts-* tags support the Vulkan SC CTS.

I don't have access to a Vulkan SC setup, so I was only able to test this command (to dump the CTS test names) with the new vulkansc-cts package:

• deqp-vksc --deqp-runmode=txt-caselist

Cc: @Flakebi

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[Flakebi]

Sounds mostly good to me, thanks!
As the packages are rather similar, it would be good to share the code for them. The cts-sources.py script is the same and the default.nix is almost identical, so it would be a shame to have the code duplicated :)

[Flakebi]

It seems like deqp-vksc does not work correctly at the moment, so I’d also be fine with just dropping it.

$ deqp-vksc -n dEQP-VKSC.info.device
…
FATAL ERROR: Couldn't match tags from sub.qpa Subprocess failed with exit code 0(0) at vktTestPackage.cpp:1009

[jljusten]

It seems like deqp-vksc does not work correctly at the moment, so I’d also be fine with just dropping it.

$ deqp-vksc -n dEQP-VKSC.info.device
…
FATAL ERROR: Couldn't match tags from sub.qpa Subprocess failed with exit code 0(0) at vktTestPackage.cpp:1009

Do you have a driver that supports Vulkan SC? I also see a similar error message, but I don't think my driver supports Vulkan SC.

I did as you suggested, and just dropped Vulkan SC support, rather than creating a new package for it. Perhaps we can add the separate package in the future if we can get a way to confirm that it is working.

I also updated the package from 1.4.1.2 to a new 1.4.1.3 tag.

[Flakebi]

Seems like we need to remove one of the two leading \n here to make nixfmt happy:

nixpkgs/pkgs/by-name/vu/vulkan-cts/vk-cts-sources.py

Line 77 in 28f541b

f.write("\n\n prePatch = ''\n");

Otherwise the change looks good to me (builds and passes tests nix-build . -A vulkan-cts.tests), thanks!

[Flakebi]

Thanks, LGTM!