test(nvn): a null texture builder is a scratch one #540
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!540
Loading…
Reference in a new issue
No description provided.
Delete branch "test/tex-builder-guard"
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
Adds a game-free test for the null texture-builder path from issue #500.
tb_or_scratch()inhost/nvn_native.c(commit0c511fd) returns a zeroed scratch builder when the game passes 0, sonvnTextureBuilderSetSwizzleno longer readsA64_MEM + 0x5c.The fixture builds the real
tb_or_scratch()andnvnTextureBuilderSetSwizzle()bodies fromhost/nvn_native.cat-O2, calls the setter with a null builder, requires exactly one diagnostic log, then checks that a real builder still receives swizzle 1/2/3/4.Test
python -I -B tests/test_nvn_tex_builder_guard.py(wired intosource-regressions.yml)tb_or_scratch) falls back to the oldTBmacro and dereferences NULL; the fixed source prints PASS.Refs #500.
The
appimagejob failed at its "Play profile" download step (the packaging workflow fetches the latest builder zip); it does not build or run the tests. The relevant checks pass:Python source checkson Ubuntu and Windows, includingCheck a null NVN texture builder is a scratch one, and the SPIR-V fixture job.