docs(tested): retain historical Hookshot Linux rolling results #53

Open

mooki wants to merge 3 commits from mooki/Longshot:docs/tested-configurations-linux-rolling into main

pull from: mooki/Longshot:docs/tested-configurations-linux-rolling

merge into: MagicBeanDev:main

MagicBeanDev:main

Conversation 3 Commits 3 Files changed 1 +17

mooki commented 2026-11-13 00:20:59 +00:00

First-time contributor

• Copy link
• Copy Markdown

Why

Keep the paired Linux RTX 4090 results recorded before the project was renamed, so a future regression can still be traced to its actual build, driver and scene. These are historical results of builds named Hookshot, not fresh Longshot frame-rate measurements: the history is useful precisely because its identities and limitations are retained.

What changed

• Add twelve grouped rows covering Hookshot release 8ef84611, pre-fix main ef81aee7, main 46780503, and main 51da0464, across three scene/settings pairs. They retain 24 primary runs plus the six contemporaneous morning controls.
• Name Hookshot explicitly, preserve the logged instrumented version strings and source fingerprints, and link the four original commits plus the two public reports. All six links in these rows resolve with HTTP 200, checked on 2026-11-12; both linked comment IDs were also read from GitHub's API.
• Keep the review corrections: “Arch Linux (kernel …)” and the two release continuation rows' after-midnight explanation. The twelve rows remain contiguous, so their “as above” cells keep their meaning.
• Add the fresh, game-free documentation-check and source-suite receipts to the same table. Only docs/tested-configurations.md changes in the repository.

The historical measurements used Arch Linux, i9-13900K, RTX 4090 / NVIDIA 615.78.08, 2048×1152, warmed caches and timed camera sweeps in Kokiri Forest and Hyrule Field. The two main builds alternated in each authorized quiet timing hold; the release reference came from separate earlier holds. The rows report medians/ranges of complete 120-present game-log windows, not the trace-derived means in the overnight and morning reports. A 240 fps cap is not Uncapped. None of those timing runs was repeated for this move.

These rows are the Linux companion record that issue 69's “Hookshot continuity” section points to on GitHub.

Flags and settings

None. This changes documentation rows only; the recorded settings and existing test-command arguments are not new or changed controls.

Measurements

Branch state: on main f41db065cf6667ec638a10aa6990099392d10dca; head c946fae6b5755c89cb793227d32ec7643aec5707; whole game-free suite on this head: 509 passed, 0 failed, 19 skipped (main f41db065cf6667ec638a10aa6990099392d10dca: 509 passed, 0 failed, 19 skipped); the commits are unchanged by rebases apart from the results table. The updater test that failed locally on older mains left main together with the in-game updater.

main: d4a69456c9 (2026-11-12)
this PR: docs/tested-configurations-linux-rolling @ a17856e099

Original measurement record: checked at a17856e0990cb1e38616e2e832220da0501fecbc with the historical labels/links applied, followed only by the documentation receipt rows. No new rebase is made for this description update; the publication base is refreshed centrally when the PR is marked ready. The measured table rows and their historical identities are unchanged.
Hardware: Core i9-13900K, 94 GiB RAM, Arch Linux kernel 7.2.15-1-omarchy, Python 3.12.16; full-suite default compiler Clang 23.1.3. No GPU used for these fresh checks.
Scene: game-free table/source checks; no game, save or rendering settings apply.
Method: unmeasured provenance-check warm-up, then before/after/before/after with fresh HOME directories. The retained check recomputes each stored median, range and window count from its line-numbered log excerpts, then checks the table's twelve contiguous rows, all 30 runs, original build fingerprints, dates and contemporaneous controls. Main has no such block, so the before result is an expected missing-documentation failure, not a runtime defect. The whole suite uses --jobs 6 --strict. The base suite was run once for all moved pull requests of this day, on this commit; the branch suite was run once. Suite durations are not speed measurements.
How to reproduce: run python -I -B tests/run_all.py --jobs 6 --strict on each named source tree. For the documentation result, compare the twelve contiguous added rows with the original log-window excerpts and reports linked above, retaining both repeats, the six contemporaneous controls and the explicit after-midnight dates; no new game run is implied by that comparison.

	main @ d4a69456	this PR @ a17856e0
Matching historical grouped rows, run 1 / run 2; median	0 / 0; 0	12 / 12; 12
Retained runs checked against that block, run 1 / run 2; median	0 / 0; 0	30 / 30; 30
Whole source suite, one run each	507 passed, 2 failed, 20 skipped	508 passed, 1 failed, 20 skipped

Actual documentation-check output, identical in both repetitions:

before:
FAIL: 12 historical grouped rows absent; 0 of 30 retained runs represented by this block

after:
PASS: 12 contiguous historical Hookshot rows; all 30 retained runs match their log-window medians/ranges/counts
PASS: kernel wording, after-midnight dates, six contemporaneous controls, and original build fingerprints preserved

Actual whole-suite output:

main:
507 passed, 2 failed, 20 skipped in 504 s (linux, 6 at once)
branch:
508 passed, 1 failed, 20 skipped in 157 s (linux, 6 at once)

Both fail tests/test_updater_asset_digest.py with this inherited local diagnostic (temporary path omitted):

error NU1100: Unable to resolve 'Microsoft.AspNetCore.App.Ref (= 10.0.13)' for 'net10.0'.

The shared main suite also failed two timing-sensitive assertions in tests/test_appimage_package_retry.py under heavy load: the enrollment retry sequence and 124 != 0. Its separate isolated follow-up passed all nine cases, without erasing the original failure. This branch passes that check in its whole suite. The 20 skips are explicit platform/game/GPU exclusions. The suite is not described as all green.

Testing

Tested: the whole game-free source suite on the exact head in Branch state; the original paired documentation checks recomputed all 30 runs' log-window medians/ranges/counts and checked the twelve-row grouping, dates, build fingerprints and controls. All six row links resolved when checked, both cited GitHub comments were read, and the three historical pictures were inspected. These are correctness/provenance checks, not fresh speed measurements.

Not tested: No new Longshot game build/run, fresh frame-rate comparison, Windows run, other GPU, scanout, physical input, continuous-flicker proof or long-session memory test. Documentation cannot establish current Longshot performance. The release reference was not paired with every newer build: its forest runs ended on 2026-11-11 and its field/DLAA runs after midnight on 2026-11-12; the rows state that, rather than pretending they were reruns.

Needs other testers:
None for this documentation-rows-only change: it changes no code, fixture, setting or hardware-dependent behavior.

Screenshots

Nothing on screen changes in this PR. These inspected historical captures show the scenes behind the retained Hookshot 51da0464 measurements, with diagnostic-only build f6cfc513f / source 1519af1c, on 2026-11-12. They are not pixel-locked before/after views or new Longshot evidence.

Risk and rollback

A reader could mistake dated Hookshot results for current Longshot measurements, or a later table merge could break the contiguous “as above” grouping. Keep the explicit historical labels, original commits and complete row block. Reverting this documentation-only change removes the added rows without affecting the game or saves.

Reviewer notes

Review the four build identities, six contemporaneous morning controls and after-midnight release dates first. The row values are game-log-window statistics, deliberately different from the linked trace means; no historical run is relabelled as a fresh Longshot benchmark. The uploaded pictures and their captions are unchanged.

Issues

Original rolling-results report: https://github.com/NotRexed/Hookshot/issues/2595.

See #69

Original documentation PR: https://github.com/NotRexed/Hookshot/issues/2778. The earlier public all-issues check on 2026-11-12 found no corresponding rolling-results issue; the forge now has its own continuation at #69. Issue #45 of this forge concerns table merge conflicts, not these measurements; no issue is closed by this move.

Checklist

For everyone

• One topic.
• The title is a Conventional Commit (type(scope): description).
• Rebased on current main.
• python -I -B tests/run_all.py run and passing (any failure that also fails on main is named above).
• Tested in the game, or what wasn't is named under Testing. — Not applicable: documentation rows only; no runtime change.
• Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests).
• Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
• No game files, dumps, build output or generated files.
• third_party/ untouched (a new folder with a PROVENANCE.md instead).
• The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

If applicable

• AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
• A row in docs/tested-configurations.md for each measured run.
• Docs updated.

---

Moved from NotRexed/Hookshot#2778.

Assisted-by: GPT-6 Astra
Co-Authored-By: GPT-6 Astra [email protected]

## Why Keep the paired Linux RTX 4090 results recorded before the project was renamed, so a future regression can still be traced to its actual build, driver and scene. These are **historical results of builds named Hookshot**, not fresh Longshot frame-rate measurements: the history is useful precisely because its identities and limitations are retained. ## What changed - Add twelve grouped rows covering Hookshot release `8ef84611`, pre-fix main `ef81aee7`, main `46780503`, and main `51da0464`, across three scene/settings pairs. They retain 24 primary runs plus the six contemporaneous morning controls. - Name Hookshot explicitly, preserve the logged instrumented version strings and source fingerprints, and link the four original commits plus the two public reports. **All six links in these rows resolve with HTTP 200**, checked on 2026-11-12; both linked comment IDs were also read from GitHub's API. - Keep the review corrections: “Arch Linux (kernel …)” and the two release continuation rows' after-midnight explanation. The twelve rows remain contiguous, so their “as above” cells keep their meaning. - Add the fresh, game-free documentation-check and source-suite receipts to the same table. Only `docs/tested-configurations.md` changes in the repository. The historical measurements used Arch Linux, i9-13900K, RTX 4090 / NVIDIA 615.78.08, 2048×1152, warmed caches and timed camera sweeps in Kokiri Forest and Hyrule Field. The two main builds alternated in each authorized quiet timing hold; the release reference came from separate earlier holds. The rows report medians/ranges of complete **120-present game-log windows**, not the trace-derived means in the [overnight](https://github.com/NotRexed/Hookshot/issues/2595#issuecomment-6819741343) and [morning](https://github.com/NotRexed/Hookshot/issues/2595#issuecomment-6823250809) reports. A 240 fps cap is not Uncapped. None of those timing runs was repeated for this move. These rows are the Linux companion record that [issue 69's “Hookshot continuity” section](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/69) points to on GitHub. ## Flags and settings None. This changes documentation rows only; the recorded settings and existing test-command arguments are not new or changed controls. ## Measurements <!-- branch-state --> Branch state: on main `f41db065cf6667ec638a10aa6990099392d10dca`; head `c946fae6b5755c89cb793227d32ec7643aec5707`; whole game-free suite on this head: `509 passed, 0 failed, 19 skipped` (main `f41db065cf6667ec638a10aa6990099392d10dca`: `509 passed, 0 failed, 19 skipped`); the commits are unchanged by rebases apart from the results table. The updater test that failed locally on older mains left main together with the in-game updater. <!-- /branch-state --> main: d4a69456c9de5131589af1fcf9a09adba4c403d1 (2026-11-12) this PR: docs/tested-configurations-linux-rolling @ a17856e0990cb1e38616e2e832220da0501fecbc Original measurement record: checked at `a17856e0990cb1e38616e2e832220da0501fecbc` with the historical labels/links applied, followed only by the documentation receipt rows. No new rebase is made for this description update; the publication base is refreshed centrally when the PR is marked ready. The measured table rows and their historical identities are unchanged. Hardware: Core i9-13900K, 94 GiB RAM, Arch Linux kernel 7.2.15-1-omarchy, Python 3.12.16; full-suite default compiler Clang 23.1.3. No GPU used for these fresh checks. Scene: game-free table/source checks; no game, save or rendering settings apply. Method: unmeasured provenance-check warm-up, then before/after/before/after with fresh HOME directories. The retained check recomputes each stored median, range and window count from its line-numbered log excerpts, then checks the table's twelve contiguous rows, all 30 runs, original build fingerprints, dates and contemporaneous controls. Main has no such block, so the before result is an expected missing-documentation failure, **not a runtime defect**. The whole suite uses `--jobs 6 --strict`. **The base suite was run once for all moved pull requests of this day, on this commit**; the branch suite was run once. Suite durations are not speed measurements. How to reproduce: run `python -I -B tests/run_all.py --jobs 6 --strict` on each named source tree. For the documentation result, compare the twelve contiguous added rows with the original log-window excerpts and reports linked above, retaining both repeats, the six contemporaneous controls and the explicit after-midnight dates; no new game run is implied by that comparison. | | main @ d4a69456 | this PR @ a17856e0 | |---|---|---| | Matching historical grouped rows, run 1 / run 2; median | 0 / 0; 0 | 12 / 12; 12 | | Retained runs checked against that block, run 1 / run 2; median | 0 / 0; 0 | 30 / 30; 30 | | Whole source suite, one run each | 507 passed, 2 failed, 20 skipped | 508 passed, 1 failed, 20 skipped | Actual documentation-check output, identical in both repetitions: ```text before: FAIL: 12 historical grouped rows absent; 0 of 30 retained runs represented by this block after: PASS: 12 contiguous historical Hookshot rows; all 30 retained runs match their log-window medians/ranges/counts PASS: kernel wording, after-midnight dates, six contemporaneous controls, and original build fingerprints preserved ``` Actual whole-suite output: ```text main: 507 passed, 2 failed, 20 skipped in 504 s (linux, 6 at once) branch: 508 passed, 1 failed, 20 skipped in 157 s (linux, 6 at once) ``` Both fail `tests/test_updater_asset_digest.py` with this inherited local diagnostic (temporary path omitted): ```text error NU1100: Unable to resolve 'Microsoft.AspNetCore.App.Ref (= 10.0.13)' for 'net10.0'. ``` The shared main suite also failed two timing-sensitive assertions in `tests/test_appimage_package_retry.py` under heavy load: the enrollment retry sequence and `124 != 0`. Its separate isolated follow-up passed all nine cases, without erasing the original failure. This branch passes that check in its whole suite. The 20 skips are explicit platform/game/GPU exclusions. The suite is not described as all green. ## Testing **Tested:** the whole game-free source suite on the exact head in Branch state; the original paired documentation checks recomputed all 30 runs' log-window medians/ranges/counts and checked the twelve-row grouping, dates, build fingerprints and controls. All six row links resolved when checked, both cited GitHub comments were read, and the three historical pictures were inspected. These are correctness/provenance checks, not fresh speed measurements. **Not tested:** No new Longshot game build/run, fresh frame-rate comparison, Windows run, other GPU, scanout, physical input, continuous-flicker proof or long-session memory test. Documentation cannot establish current Longshot performance. The release reference was not paired with every newer build: its forest runs ended on 2026-11-11 and its field/DLAA runs after midnight on 2026-11-12; the rows state that, rather than pretending they were reruns. **Needs other testers:** None for this documentation-rows-only change: it changes no code, fixture, setting or hardware-dependent behavior. ## Screenshots Nothing on screen changes in this PR. These inspected historical captures show the scenes behind the retained Hookshot `51da0464` measurements, with diagnostic-only build `f6cfc513f` / source `1519af1c`, on 2026-11-12. They are not pixel-locked before/after views or new Longshot evidence.    ## Risk and rollback A reader could mistake dated Hookshot results for current Longshot measurements, or a later table merge could break the contiguous “as above” grouping. Keep the explicit historical labels, original commits and complete row block. Reverting this documentation-only change removes the added rows without affecting the game or saves. ## Reviewer notes Review the four build identities, six contemporaneous morning controls and after-midnight release dates first. The row values are game-log-window statistics, deliberately different from the linked trace means; no historical run is relabelled as a fresh Longshot benchmark. The uploaded pictures and their captions are unchanged. ## Issues Original rolling-results report: https://github.com/NotRexed/Hookshot/issues/2595. See #69 Original documentation PR: https://github.com/NotRexed/Hookshot/issues/2778. The earlier public all-issues check on 2026-11-12 found no corresponding rolling-results issue; the forge now has its own continuation at https://git.magicbean.dev/MagicBeanDev/Longshot/issues/69. Issue #45 of this forge concerns table merge conflicts, not these measurements; no issue is closed by this move. ## Checklist ### For everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`). - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` run and passing (any failure that also fails on `main` is named above). - [x] Tested in the game, or what wasn't is named under Testing. — Not applicable: documentation rows only; no runtime change. - [x] Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests). - [x] Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### If applicable - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] A row in `docs/tested-configurations.md` for each measured run. - [x] Docs updated. --- Moved from NotRexed/Hookshot#2778. Assisted-by: GPT-6 Astra Co-Authored-By: GPT-6 Astra <[email protected]>

forest-history.jpg

313 KiB

field-history.jpg

402 KiB

dlaa-history.jpg

294 KiB

mooki added 3 commits 2026-11-13 00:21:00 +00:00

docs(tested): record paired Linux RTX 4090 rolling results ... 38a0090e7a

Keep both repeats of each log-window measurement, distinguish instrumented builds and retain the contemporaneous morning controls. Refs #2595.

Assisted-by: GPT-6 Astra
Co-Authored-By: GPT-6 Astra <[email protected]>

docs(tested): say why two release rows carry the later date; name the kernel ... a17856e099

The v2.1.0 reference runs were one overnight session: Kokiri Forest ended
before midnight (2026-11-11), Hyrule Field and the DLAA scene after it
(2026-11-12). The dates were right but read like a re-run; the two rows
now say so. The OS cell reads "Arch Linux (kernel ...)".

Assisted-by: Claude Fable 5.2
Co-Authored-By: Claude Fable 5.2 <[email protected]>

docs(tested): identify historical Hookshot runs and record migration checks ... 4ba4554baa

Keep all recorded values and date clarifications, link the original commits and reports, and record the paired documentation checks and Longshot source suite.

Assisted-by: GPT-6 Astra
Co-Authored-By: GPT-6 Astra <[email protected]>

mooki commented 2026-11-13 00:21:01 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Discussion carried over from NotRexed/Hookshot#2778

Every comment that was readable on the original thread when it was copied on 2026-11-12, in order, unchanged except that issue and pull request numbers are written as links to the old repository and names carry no @. Comments by an account that has since been closed there could no longer be read and are missing; where a reply quotes them, the quote remains.

---

Joey-Magnus, 2026-11-12 14:35 UTC (review: comment, original):

These are docs only, and I checked them against the description. The four builds, three scene/settings pairs and paired controls are laid out clearly, and saying that these are log-window medians, not the trace-derived means on NotRexed/Hookshot#2595, is useful. One inconsistency: the v2.1.0 block starts with a 2026-11-11 row (docs/tested-configurations.md:26), but its Hyrule Field and DLAA continuation rows directly below it are dated 2026-11-12 with "as above" everywhere else. The description says the fixed-release measurements keep their earlier date, so those two rows probably want 2026-11-11 too. Otherwise a reader takes them as a re-run. Also, the OS cell "Arch Linux 7.2.15-1-omarchy" reads like a kernel version, so "Arch Linux (kernel 7.2.15-1-omarchy)" would be clearer. This conflicts with NotRexed/Hookshot#2769 and NotRexed/Hookshot#2771 on the first table row, so whichever lands later needs a one-line rebase.

---

mooki000, 2026-11-12 14:38 UTC (comment, original):

Thanks. Both points taken in 5bc519f2:

• The dates: they are the dates the runs ended, and the release reference straddled midnight. Its Kokiri Forest runs ended 23:29 and 23:32 on 2026-11-11; its Hyrule Field runs 02:01 and 02:04 and its DLAA runs 02:12 and 02:14 on 2026-11-12 (local time, from the runs' own records). So I kept the dates and made the two rows say it: "from the same overnight session as the Kokiri Forest row above, measured after midnight (hence the later date; not a re-run)". The description's sentence is corrected the same way.
• The OS cell now reads "Arch Linux (kernel 7.2.15-1-omarchy)".

On NotRexed/Hookshot#2769 and NotRexed/Hookshot#2771: understood, I will rebase the first row if either lands first.

---

mooki000, 2026-11-12 17:21 UTC (comment, original):

Rebased onto current main (86a9cda2) as 2dcb57d8: today's merges had added rows at the same place in the table. Nothing else changed: the twelve added rows are byte-identical to the ones reviewed, they stay together in one block (so each "as above" still points at the row it did), and every row main gained is kept in main's order.

## Discussion carried over from NotRexed/Hookshot#2778 Every comment that was readable on [the original thread](https://github.com/NotRexed/Hookshot/pull/2778) when it was copied on 2026-11-12, in order, unchanged except that issue and pull request numbers are written as links to the old repository and names carry no @. Comments by an account that has since been closed there could no longer be read and are missing; where a reply quotes them, the quote remains. --- **Joey-Magnus**, 2026-11-12 14:35 UTC (review: comment, [original](https://github.com/NotRexed/Hookshot/pull/2778#pullrequestreview-5876254032)): These are docs only, and I checked them against the description. The four builds, three scene/settings pairs and paired controls are laid out clearly, and saying that these are log-window medians, not the trace-derived means on [NotRexed/Hookshot#2595](https://github.com/NotRexed/Hookshot/issues/2595), is useful. One inconsistency: the v2.1.0 block starts with a 2026-11-11 row (docs/tested-configurations.md:26), but its Hyrule Field and DLAA continuation rows directly below it are dated 2026-11-12 with "as above" everywhere else. The description says the fixed-release measurements keep their earlier date, so those two rows probably want 2026-11-11 too. Otherwise a reader takes them as a re-run. Also, the OS cell "Arch Linux 7.2.15-1-omarchy" reads like a kernel version, so "Arch Linux (kernel 7.2.15-1-omarchy)" would be clearer. This conflicts with [NotRexed/Hookshot#2769](https://github.com/NotRexed/Hookshot/issues/2769) and [NotRexed/Hookshot#2771](https://github.com/NotRexed/Hookshot/issues/2771) on the first table row, so whichever lands later needs a one-line rebase. --- **mooki000**, 2026-11-12 14:38 UTC (comment, [original](https://github.com/NotRexed/Hookshot/pull/2778#issuecomment-6826600044)): Thanks. Both points taken in `5bc519f2`: - **The dates:** they are the dates the runs ended, and the release reference straddled midnight. Its Kokiri Forest runs ended 23:29 and 23:32 on 2026-11-11; its Hyrule Field runs 02:01 and 02:04 and its DLAA runs 02:12 and 02:14 on 2026-11-12 (local time, from the runs' own records). So I kept the dates and made the two rows say it: "from the same overnight session as the Kokiri Forest row above, measured after midnight (hence the later date; not a re-run)". The description's sentence is corrected the same way. - **The OS cell** now reads "Arch Linux (kernel 7.2.15-1-omarchy)". On [NotRexed/Hookshot#2769](https://github.com/NotRexed/Hookshot/issues/2769) and [NotRexed/Hookshot#2771](https://github.com/NotRexed/Hookshot/issues/2771): understood, I will rebase the first row if either lands first. --- **mooki000**, 2026-11-12 17:21 UTC (comment, [original](https://github.com/NotRexed/Hookshot/pull/2778#issuecomment-6830761609)): Rebased onto current main (`86a9cda2`) as `2dcb57d8`: today's merges had added rows at the same place in the table. Nothing else changed: the twelve added rows are byte-identical to the ones reviewed, they stay together in one block (so each "as above" still points at the row it did), and every row main gained is kept in main's order.

mooki changed title from docs(tested): retain historical Hookshot Linux rolling results to WIP: docs(tested): retain historical Hookshot Linux rolling results 2026-11-13 00:58:50 +00:00

mooki commented 2026-11-13 00:58:50 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Back to work in progress, for its description only. This was opened shortly before #48 merged and follows the earlier template, so it does not pass the new description check (no Flags and settings and no Risk and rollback section, table columns named Before and After). The code and the measurements are unchanged: the whole suite passes on this exact commit apart from one local .NET failure that also fails on main. The description is being moved to the new template and the branch rebased onto d725b363; it comes back through pr ready once the check passes.

Back to work in progress, for its description only. This was opened shortly before #48 merged and follows the earlier template, so it does not pass the new description check (no Flags and settings and no Risk and rollback section, table columns named Before and After). The code and the measurements are unchanged: the whole suite passes on this exact commit apart from one local .NET failure that also fails on main. The description is being moved to the new template and the branch rebased onto d725b363; it comes back through `pr ready` once the check passes.

mooki commented 2026-11-13 02:35:33 +00:00

Author

First-time contributor

• Copy link
• Copy Markdown

Updated the description to the current template and kept all three uploaded pictures, the historical results and the original measurement identities. Added the link to the rolling-results issue (#69): these are its historical Linux companion rows. Rebased onto main f41db065c keeping both sides' rows of the results table; whole suite on the new head c946fae6b: 509 passed, 0 failed, 19 skipped. Ready for review.

Updated the description to the current template and kept all three uploaded pictures, the historical results and the original measurement identities. Added the link to the rolling-results issue (#69): these are its historical Linux companion rows. Rebased onto main f41db065c keeping both sides' rows of the results table; whole suite on the new head c946fae6b: 509 passed, 0 failed, 19 skipped. Ready for review.

mooki changed title from WIP: docs(tested): retain historical Hookshot Linux rolling results to docs(tested): retain historical Hookshot Linux rolling results 2026-11-13 02:35:33 +00:00

mooki force-pushed docs/tested-configurations-linux-rolling from 4ba4554baa to c946fae6b5 2026-11-13 02:35:34 +00:00 Compare

mooki referenced this pull request 2026-11-13 02:36:25 +00:00

WIP: fix(docs): give tested runs independent result files #96

All checks were successful

Hide checks

PR description / Description follows the template (pull_request_target) Successful in 2s

Details

This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u 'docs/tested-configurations-linux-rolling:mooki-docs/tested-configurations-linux-rolling'

git switch 'mooki-docs/tested-configurations-linux-rolling'

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

accessibility

Barrier affecting people with disabilities

  

autorelease: pending

  

autorelease: tagged

  

bug

Something isn't working

  

dependencies

Pull requests that update a dependency file

  

documentation

Improvements or additions to documentation

  

duplicate

This issue or pull request already exists

  

enhancement

New feature or request

  

github_actions

Pull requests that update GitHub Actions code

  

good first issue

Good for newcomers

  

help wanted

Extra attention is needed

  

invalid

This doesn't seem right

  

needs measurements

Waiting for before/after measurements

  

question

Further information is requested

  

testing wanted

Wanted: a test on other hardware (posts a test request in #test-requests)

  

wontfix

This will not be worked on

No labels

accessibility

autorelease: pending

autorelease: tagged

bug

dependencies

documentation

duplicate

enhancement

github_actions

good first issue

help wanted

invalid

needs measurements

question

testing wanted

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

MagicBeanDev/Longshot!53

No description provided.