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!364
Loading…
Reference in a new issue
No description provided.
Delete branch "GrimVisage/Longshot:docs/tested-market-231-232"
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
The tested configurations had no 6-core desktop CPU on Linux in the Market for #231 or #232. These are the six runs behind the measurements posted on #231 and #232, recorded as
docs/tested-configurations.mdasks.What changed
docs/tested/,2026-11-13-market-replay-prs-grimvisage-run01.mdtorun06.md, one run each, in the format ofdocs/tested/README.md: main5a8ae7e3, #231 at9951d916and #232 at3ccb48a8, Ryzen 5 5600X and RX 9070 XT on Fedora 45 (RADV 26.2.6), the Market standing for 120 s, uncapped. The frozen table is untouched and no assembled view is committed.Flags and settings
None.
Measurements
A docs change: measured by its check (CONTRIBUTING.md, "Measurements":
docs, test output on main and with this PR).main:
cf605c85(the branch's base)this PR: docs/tested-market-231-232 @
13b02078Hardware: Ryzen 5 5600X, 31 GB, Fedora 45 (kernel 7.3.3), Python 3.15.2
Scene: none (game-free checks)
Method:
python -I -B tests/test_tested_configurations.py, andpython -I -B tests/run_all.pyon this PR with the failing checks run again on mainHow to reproduce: the two commands above from the repository root
cf605c8513b02078tests/test_tested_configurations.pytests/run_all.pytest_menu_keys,test_module_ids,test_pad_layoutfailThe runs the files record, with their method and log lines, are in the comments linked under Why.
Testing
Tested: the files' format check (
tests/test_tested_configurations.py) and the whole game-free suite on Linux (Fedora 45); the three failures there also fail on maincf605c85on this PC. The runs themselves were made in the game on this PC (Ryzen 5 5600X, RX 9070 XT, RADV 26.2.6), as the comments on #231 and #232 describe.Not tested: the website's catalogue built from these files (it reads
docs/tested/directly; not run here).Needs other testers: None
Screenshots
Nothing on screen.
Risk and rollback
Docs only: nothing the game, the builds or the checks run changes. Reverting the commit removes the files.
Reviewer notes
Each file repeats the run's context in full, as
docs/tested/README.mdasks; the rows differ in their run number, time and numbers.Issues
See #231
See #232
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.docs/tested/for each new measured run (format indocs/tested-configurations.md; no appended row or assembled view).🤖 Generated with Claude Code
WIP: docs(tested): #231 and #232 in the Market on a 6-core Linux desktop, interleaved against their baseto docs(tested): #231 and #232 in the Market on a 6-core Linux desktop, interleaved against their baseView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.