test(release): the git-cliff stand-in is a .cmd on Windows, which can start it #145
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!145
Loading…
Reference in a new issue
No description provided.
Delete branch "d4nkn3ss/Longshot:fix/test-release-cliff-stub-windows"
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_release.py'stest_the_first_notes_give_git_cliff_no_range(added in #116) errors on every Windows run: its git-cliff stand-in is a#!/bin/shscript, which Windows can't start.What changed
tests/test_release.py, on Windows the stand-in isgit-cliff-stub.cmd(@echo %*), which echoes its arguments on one line; the test reads them with.split()either way. Elsewhere the shell script stays as it was.Flags and settings
None
Measurements
main:
e28236b4(2026-11-12)this PR: fix/test-release-cliff-stub-windows @
ef339b94Hardware: Windows 11, Python 3.12 from python.org
Scene: n/a (game-free)
Method:
python -I -B tests/test_release.py Bump.test_the_first_notes_give_git_cliff_no_rangeon both sidesHow to reproduce: on Windows, the command above
e28236b4ef339b94test_the_first_notes_give_git_cliff_no_rangeOSError: [WinError 193] %1 is not a valid Win32 applicationTesting
Tested: the row above on Windows 11.
Full suite:
python -I -B tests/run_all.pyon this branch @ef339b94: 500 passed, 3 failed, 35 skipped, the same three as main @e28236b4:tests/test_check_third_party.py(#80),tests/test_setup_runtime.py(#118) andtests/test_release.py, whose other failures are #119 (the SHA256SUMS fixture) and, from PowerShell, the missingopenssl(#144).Not tested: Linux and macOS: the shell-script branch is the code as it was.
Needs other testers: None
Screenshots
Nothing on screen
Risk and rollback
Tests 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.🤖 Generated with Claude Code
Requesting changes at
ef339b94. The .cmd does fix WinError193 for an ASCII temporary path, but its output is not the UTF-8 that release.notes requires.This is a focused authored-fixture check; no real release creation, token operation or game run. I did not repeat the whole suite or change its assertions.
@ -220,1 +218,3 @@stub.chmod(0o755)if os.name == "nt": # (Windows starts a .cmd, not a #! script: WinError 193. It echoes its arguments on one line)stub = self.dir / "git-cliff-stub.cmd"stub.write_text("@echo %*\r\n", encoding="utf-8")[P2] This echoes in the Windows console code page, but release.notes decodes UTF-8. Reproduced with TEMP/TMP containing Zoë: byte 0x89 in the --config path causes UnicodeDecodeError, then p.stdout.strip fails because stdout is None. The identical case passes with an ASCII TEMP. Please emit explicit UTF-8 and cover a Unicode path; PR255 follow-up01943afa already does this and passes the same probe.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.