test(setup): test_setup_runtime cuts builder_ready() alone, not up to manifest_url() #118
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!118
Loading…
Reference in a new issue
No description provided.
Delete branch "d4nkn3ss/Longshot:fix/test-setup-runtime-cut"
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_setup_runtime.pyfails onmainon Windows, the only platform it runs on, so the check that a self-contained Builder has all its startup files has been off since #13.What changed
tests/test_setup_runtime.pycutsbuilder_ready()out ofbuilder/setup/setup.cup to its own closing brace, instead of up tomanifest_url(). #13 added#define LAUNCHER_RELEASES L"https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/releases"between the two functions, so the test took that URL for one of the Builder's required files, and creating a file of that name failed (OSError: [Errno 22] Invalid argument).Flags and settings
None
Measurements
main:
94bbc205(2026-11-12)this PR: fix/test-setup-runtime-cut @
0b2d598dHardware: Windows 11, Python 3.12 from python.org, llvm-mingw clang 23 (
--cxx clang++)Scene: n/a (game-free)
Method:
python -I -B tests/run_all.py setup_runtimeonce on each side, same checkoutHow to reproduce: on Windows with clang++ on PATH,
python -I -B tests/run_all.py setup_runtime94bbc2050b2d598dtests/test_setup_runtime.pyOSError: [Errno 22] Invalid argument: '...\Builder space é\https:\git.magicbean.dev\...\releases'Testing
Tested: the command above on Windows 11 on both sides; the cut now ends at
builder_ready()'sreturn 1; }.tests/test_setup_runtime_paths.pypasses on both.Full suite:
python -I -B tests/run_all.pyon this branch @0b2d598d, Windows 11: 494 passed, 2 failed, 35 skipped. The failures:tests/test_check_third_party.py(fixed by #80) andtests/test_release.py(fixed by #119), both failing onmainthe same way.Not tested: Linux: the test skips itself there (
RUN_ALL_SKIP), as before.Needs other testers: None
Screenshots
Nothing on screen
Risk and rollback
Test-only; reverting the commit is enough.
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
Full game-free suite run on this branch (Windows 11); the results and the failures that also fail on main are now under Testing. Marking ready.
WIP: test(setup): test_setup_runtime cuts builder_ready() alone, not up to manifest_url()to test(setup): test_setup_runtime cuts builder_ready() alone, not up to manifest_url()d4nkn3ss referenced this pull request2026-11-13 07:30:02 +00:00
Superseded by main:
839e85ff(removing the Python builder) changed the same line to cutbuilder_ready()up to#define LAUNCHER_DOWNLOAD, andtests/test_setup_runtime.pynow passes on Windows on main @9a186f71(python -I -B tests/run_all.py setup_runtime: 2 passed). This PR's cut (to the function's own closing brace) would only guard against a future string between the two; not worth a review on its own, so it can be closed.View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.