KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Encoding Video tests crashing on latest drivers in CI
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
In the last few days, we have started to hit CI failures on the following tests
- NegativeVideo.EncodeRateControlH264ConstantQpNonZero
- NegativeVideo.EncodeRateControlH265ConstantQpNonZero
- NegativeVideo.EncodeRateControlH264InvalidCodecInfo
- NegativeVideo.EncodeRateControlH265InvalidCodecInfo
with stack dumps like
```
ERROR: return code 3 (0x3) - details on failing tests follow
ERROR: ----stderr---------------------------------------------------
abort() has been called
ERROR: -------------------------------------------------------------
ERROR: vvl: CRASH - test NegativeVideo.EncodeRateControlH264InvalidCodecInfo never completed
------------------------------------------------------------
[ RUN ] NegativeVideo.EncodeRateControlH264InvalidCodecInfo
C:\j\vz1\Debug64\Vulkan-ValidationLayers\tests\framework\binding.cpp(1751): error: Expected equality of these values:
VK_SUCCESS
vk::EndCommandBuffer(handle())
Which is: VK_ERROR_INITIALIZATION_FAILED
```
running on the `NVIDIA GeForce RTX 2080` family HW with the latest NDA drivers
(https://github.com/LunarG/VulkanTests/pull/636)
Contributor guide
Research direction
Start with the four NegativeVideo tests named in the report and the failure at tests/framework/binding.cpp:1751. Reproduce them in CI on NVIDIA GeForce RTX 2080 hardware with the latest NDA drivers, then determine why vk::EndCommandBuffer returns VK_ERROR_INITIALIZATION_FAILED. Done means the affected tests complete without aborting or producing the reported failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100