test: restore renderer regressions after main changes #1498
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!1498
Loading…
Reference in a new issue
No description provided.
Delete branch "test/renderer-regression-fixtures"
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?
Recent target-pool, HDR and host-startup changes left several source-slicing regression fixtures unable to compile or reach their assertions. Restore those fixtures so CI can exercise the current renderer again, retaining their original behavior checks.
<algorithm>directly for FSR math.Only seven test files change; no production behavior, dependencies, game assets or generated output change.
Validation at
00ebb7fon main8240446: all seven affected tests pass with Windows LLVM and Linux GCC. The originala34542afixtures fail in all seven negative controls. Four production mutations (BC fallback order, recording reset, HDR output width, HDR-toggle recreation) are detected by assertion failures; sources were restored afterward. The full Windows strict suite reports 214 passed / 3 failed / 22 skipped. The three remaining local limitations are NUP symlink privileges, the legacy FPS fixture's missing initializer_list include, and native Windows SDK precompilation; this does not claim a green full suite. Linux Clang is unavailable on the test host. Exact-head fork workflows follow.The duplicate formatter currently blocking the standalone backend build is repaired separately in #1496; this test-maintenance PR does not include that production fix. No game run is claimed for this fixtures-only change.
Current head
1ad4179is based on mainb2e1c5a, including merged #1496. Two additional CI portability repairs are included:The earlier full-suite214/3/22 result belongs to00ebb7f; the two portability repairs have separate Linux causal checks and exact-head workflows are redispatched. Eight fixture files plus one workflow change; production sources remain unchanged.
Current-head validation
Current head
1ad4179, based on mainb2e1c5a. Earlier local/runtime results describe their recorded source hashes.Fork runs are separate from upstream Actions approval; no maintainer approval gate is bypassed.