test(vk): the texture staging check declares LogLevel and logf_at again, failing on main since #177 #202
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 project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!202
Loading…
Reference in a new issue
No description provided.
Delete branch "dyst/Longshot:fix/staging-check-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.pyhas failed on main since #177, on Windows and Linux: the cut ofstaging()it compiles now callslogf_at(log_debug, ...), which its fixture doesn't declare. A check that fails on main hides any real regression in texture staging, and it is one of the sanitizer lane's checks (#29).What changed
tests/texture_staging_publication_test.cppdeclaresLogLeveland stubslogf_atbeside itslogfstub, asgpu/vk/vk_internal.hdeclares them. Nothing else in the check changes.Flags and settings
None
Measurements
main:
0c74253d(2026-11-13)this PR: fix/staging-check-log-levels @
74d9a96cHardware: Ryzen 9 3900X, 64 GB, Windows 11; Linux in Docker (python:3.12, g++)
Scene: none: game-free. The texture staging check, compiled and run
Method:
python -I -B tests/run_all.py texture_staging_publicationtwice on each, Windows (the Builder's clang++, its Vulkan headers); on Linux the check run directly, plain and with--sanitize, with the pinned Vulkan headers throughscripts/fetch_commit.shHow to reproduce:
python -I -B tests/run_all.py texture_staging_publicationon each0c74253d74d9a96cTesting
Tested: the runs above;
tests/run_all.py, the whole suite, on this branch and on main0c74253d, Windows (483 passed and 6 failed on main, 484 passed and 5 failed here: this check is the one fixed; test_check_third_party, test_display_pointer, test_fpx_sticky, test_release and test_spawn_emit fail on main too).Not tested: in the game (a test fixture only).
Needs other testers: None
Screenshots
Nothing on screen.
Risk and rollback
None for the game: only the check's fixture changes. Reverting the commit brings the failure back.
Reviewer notes
#177's own run was on Linux without the Vulkan headers, where this check skips, so the break didn't show there.
tests/test_log_levels.py(from #177) covers the reallogf_at; this fixture only needs it to exist.Issues
None
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.🤖 Generated with Claude Code
WIP: test(vk): the texture staging check declares LogLevel and logf_at again, failing on main since #177to test(vk): the texture staging check declares LogLevel and logf_at again, failing on main since #177Approve. This is the one to keep of the three duplicates (this PR, #195 and #215). All three make the same two-line change.
What's good
enum LogLevel : int { log_error, log_warn, log_info, log_debug, log_trace };andvoid logf_at(LogLevel, const char*, ...)are exactly whatgpu/vk/vk_internal.h:36-37declares on main: same underlying type, same enumerator order, same signature. The real definition is ingpu/vk/vk_main.cpp:125.staging()ingpu/vk/vk_texture.cpp:506callslogf_at(log_debug, ...)(the slow-arena line), and the check cuts that function. The source comment names that call correctly.flush_mapped_rangeinvk_vma.cpp, the other function cut from that file, doesn't log at a level.--sanitize), and the description is accurate. The fixture line it touches is unchanged on main@origin, so it applies cleanly.Must change
Should change