• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

shader-slang / slang-rhi / 28387478726
67%

Build:
DEFAULT BRANCH: main
Ran 29 Jun 2026 05:17PM UTC
Jobs 3
Files 256
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

29 Jun 2026 04:33PM UTC coverage: 67.103% (-1.2%) from 68.301%
28387478726

push

github

web-flow
Vulkan: support VK_KHR_shader_abort + VK_KHR_device_fault (#782)

* Vulkan: enable VK_KHR_shader_abort + VK_KHR_device_fault for runtime abort testing

Adds device-side plumbing so a shader calling abort() (lowered to OpAbortKHR)
can be dispatched, the resulting device loss observed, and the abort message
read back via VK_KHR_device_fault. A single Feature::ShaderAbort is reported
only when the full extension chain (shader_abort, which hard-depends on
device_fault and shader_constant_data) is available, and the abort message is
surfaced through the existing debug-message callback on device loss.

Requires bumping the Vulkan-Headers dependency v1.4.318 -> v1.4.347, the
minimal release that defines VK_KHR_shader_abort; all new code is
#ifdef-guarded so older header overrides still compile.

Prerequisite for shader-slang/slang#11790.

Co-authored-by: Harsh Aggarwal <haaggarwal@nvidia.com>

* Address review: stabilize Feature value, require shaderConstantData, report fence-wait device loss

- Append Feature::ShaderAbort at the end of SLANG_RHI_FEATURES rather than in the
  Vulkan section, so the numeric values of existing enumerators stay stable
  (Feature is part of the public API).
- Require the shaderConstantData feature bit (not just the extension) before
  reporting Feature::ShaderAbort, and enable all three extensions uniformly via
  addFeatureExtension.
- Guard reportShaderAbortMessage on both VK_KHR_device_fault and VK_KHR_shader_abort,
  since VkDeviceFaultShaderAbortMessageInfoKHR comes from shader_abort.
- Report device loss from DeviceImpl::waitForFences instead of failing silently, so a
  caller waiting on timeline fences after an aborting dispatch also sees the abort message.

Co-authored-by: Harsh Aggarwal <haaggarwal@nvidia.com>

* Address review feedback on VK_KHR_shader_abort enablement

- Drop the #ifdef VK_KHR_shader_abort / VK_KHR_device_fault / VK_KHR_shader_constant_data
  guards: slang-rhi pins its own Vulkan-Headers, so these symb... (continued)

12362 of 22596 branches covered (54.71%)

Branch coverage included in aggregate %.

11 of 43 new or added lines in 3 files covered. (25.58%)

5 existing lines in 2 files now uncovered.

36790 of 50653 relevant lines covered (72.63%)

268994.55 hits per line

Uncovered Changes

Lines Coverage ∆ File
27
60.56
-16.51% src/vulkan/vk-device.cpp
5
49.09
-12.59% src/vulkan/vk-utils.cpp

Coverage Regressions

Lines Coverage ∆ File
4
72.27
-2.1% src/cuda/cuda-query.cpp
1
49.09
-12.59% src/vulkan/vk-utils.cpp
Jobs
ID Job ID Ran Files Coverage
2 linux-x86_64 - 28387478726.2 29 Jun 2026 05:17PM UTC 175
63.8
GitHub Action Run
3 windows-x86_64 - 28387478726.3 29 Jun 2026 05:50PM UTC 230
67.61
GitHub Action Run
1 macos-aarch64 - 28038916012.1 23 Jun 2026 04:54PM UTC 168
38.07
GitHub Action Run
Source Files on build 28387478726
  • Tree
  • List 256
  • Changed 10
  • Source Changed 4
  • Coverage Changed 9
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #28387478726
  • fb908a7c on github
  • Prev Build on main (#28385102034)
  • Next Build on main (#28454101731)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc