KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Missing vkResetQueryPool checks
Open
Incomplete
Threading
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
- [x] VUID-vkResetQueryPool-firstQuery-02741
- [ ] VUID-vkResetQueryPool-firstQuery-02742
For `02741` it is just the same as `VUID-vkDestroyQueryPool-queryPool-00793`
For `02742` not sure how possible, but we have threading stuff probably similar
Contributor guide
Research direction
Start with the Vulkan Validation Layers handling for vkResetQueryPool and compare the existing VUID-vkResetQueryPool-firstQuery-02741 coverage with VUID-vkDestroyQueryPool-queryPool-00793. Investigate the threading-related validation mentioned for VUID-vkResetQueryPool-firstQuery-02742. Done means both unchecked VUIDs have appropriate validation and corresponding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100