test(vk): the texture staging check's fixture has the log levels the cut code logs at #215
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!215
Loading…
Reference in a new issue
No description provided.
Delete branch "TrashPanda/Longshot:test/texture-staging-log-levels"
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?
Why
tests/test_texture_staging_publication.pyfails onmainwherever Vulkan headers are found: the code it cuts fromvk_texture.cpplogs throughlogf_at(log_debug, ...)since the log levels (#177), and its fixture only haslogf. Without headers the check is skipped, so CI does not see it.What changed
tests/texture_staging_publication_test.cppgets theLogLevelenum and alogf_atstand-in, as ingpu/vk/vk_internal.h.Flags and settings
None
Measurements
main:
2331f46c(2026-11-13)this PR: test/texture-staging-log-levels @
b9c5c733No speed numbers: a test fixture only. The check's result on both sides:
2331f46cb9c5c733tests/test_texture_staging_publication.py(Vulkan headers found)Testing
Tested:
python -I -B tests/run_all.py texture_staging_publicationon Linux (CachyOS, Python 3.14, Khronos Vulkan-Headers): fails onmain@2331f46c('logf_at' was not declared in this scope), passes on this branch.Not tested: nothing else: no game code changes.
Needs other testers: None
Screenshots
Nothing on screen
Risk and rollback
None: only the check's fixture changes. Reverting the commit is enough.
Reviewer notes
Found while porting the Hookshot PRs in #209, which names it as one of the failures shared with
main.Issues
See #209
Checklist
For everyone
type(scope): description).main.python -I -B tests/run_all.pyrun and passing (any failure that also fails onmainis named above).third_party/untouched (a new folder with aPROVENANCE.mdinstead).If applicable
Assisted-by:/Co-Authored-By:trailers.tests/that reads changed source updated in this PR, not weakened.This duplicates @dyst's #202, which was opened first and makes the same change (
LogLeveland alogf_atstub intests/texture_staging_publication_test.cpp), and has also been run on Windows. Please take #202; this one can be closed. I opened it before checking the open PRs for the same failure.TrashPanda referenced this pull request2026-11-13 15:16:57 +00:00
This duplicates #202, which makes the same change, so keep #202 and close this one.
All three PRs (#195, #202 and #215) add the same
LogLevelenum andlogf_atstub, and all matchgpu/vk/vk_internal.h:36-37exactly, so this code is correct too. 202 is the one to keep because it has the most thorough testing (Windows and Linux, plain and sanitized) and a description that names the call site correctly (staging()ingpu/vk/vk_texture.cpp).Pull request closed