Skip to content

test: match memory-trim checks to resized BC3 scratch uploads - #806

Merged
NotRexed merged 1 commit into
NotRexed:mainfrom
monsterlag:fix/bc3-resized-trim-check
Nov 8, 2026
Merged

NotRexed merged 1 commit into
NotRexed:mainfrom
monsterlag:fix/bc3-resized-trim-check

Conversation

@monsterlag

Copy link
Copy Markdown
Contributor

The BC3 upload paths now pass their resize mode to bc_scratch_layout, but test_mem_trim.py still 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 false is rejected by the updated check. No production code, native compiler or GPU is involved.

@NotRexed
NotRexed merged commit c39a418 into NotRexed:main Nov 8, 2026
9 checks passed
madebyjordan added a commit to madebyjordan/Longshot that referenced this pull request Nov 9, 2026
Longshot tags a release after its build is played. The release workflow
(semantic-release) only runs by hand, and the AppImage release job waits for
vars.CI_RELEASE_LINUX like the Windows one: its AppImage would update from
Hookshot's releases. CHANGELOG and PICKS updated (test fix from NotRexed#806).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants