test(nvn): cover every guarded memory-pool accessor #541
No reviewers
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot!541
Loading…
Reference in a new issue
No description provided.
Delete branch "test/pool-guard-coverage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Extends the test from #287 / PR #510 to every memory-pool accessor guarded by
no_pool()inhost/nvn_native.c:nvnMemoryPoolGetFlags,nvnMemoryPoolGetSize,nvnMemoryPoolMap,nvnMemoryPoolGetBufferAddressandnvnMemoryPoolInvalidateMappedRange.Null calls answer 0 or return without touching memory; a real pool still returns its flags, size, mapped pointer and GPU address. The fixture is built from the real function bodies at
-O2.Test
python -I -B tests/test_nvn_null_pool.py(existing CI step)Refs #287.
The
appimagejob is the packaging workflow; it fails onmainat the same AppImage step too. The relevant checks pass:Python source checkson Ubuntu and Windows, including the extendedCheck a null NVN memory pool is answered, not dereferenced, and the SPIR-V fixture job.