test: match memory-trim checks to resized BC3 scratch uploads #806
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!806
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/bc3-resized-trim-check"
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?
The BC3 upload paths now pass their resize mode to
bc_scratch_layout, buttest_mem_trim.pystill counts the old zero-argument call. The source check therefore fails on the released v2.0.5 code on both CI platforms.Check the actual ASTC upload and texture-copy functions separately. Each must return on scratch-allocation failure and pass its own texture's resize flag. The other memory-trim checks are preserved.
Validation: the strict runner passes on Windows and Linux. The unmodified v2.0.5 test reproduces the reported CI failure; removing either guard or replacing either resize argument with
falseis rejected by the updated check. No production code, native compiler or GPU is involved.