Slow test suite takes 66 min: start routes from intermediate points #24

New issue

Open

opened 2026-10-29 16:47:14 +00:00 by Gatchan · 0 comments

Gatchan commented

2026-10-29 16:47:14 +00:00

Owner

ctest -L slow (release, -j2) now takes ~66 min, mostly narshe_to_world_map (route, movie replay and route_ports_on, ~15 min each per version), because every route replays from power-on.

Options: (1) start points = in-memory savestates are not portable, but SRAM files written at save points by routes are (movies already support an SRAM start); (2) chain routes from the end state of the previous one inside one process (one replay per version for all routes); (3) a nightly label for the longest tests.

Acceptance: full suite under 20 min without losing coverage. Related: #22 (late-game start points).

`ctest -L slow` (release, -j2) now takes ~66 min, mostly `narshe_to_world_map` (route, movie replay and route_ports_on, ~15 min each per version), because every route replays from power-on. Options: (1) start points = in-memory savestates are not portable, but SRAM files written at save points by routes are (movies already support an SRAM start); (2) chain routes from the end state of the previous one inside one process (one replay per version for all routes); (3) a `nightly` label for the longest tests. Acceptance: full suite under 20 min without losing coverage. Related: #22 (late-game start points).

Gatchan added this to the Phase 1 - scaffold milestone

2026-10-29 16:47:14 +00:00

Gatchan added the

perf

validation

labels

2026-10-29 16:47:14 +00:00

Gatchan referenced this issue

2026-10-29 17:08:46 +00:00

Routes leave game-made SRAM saves; next routes start from them #26

Gatchan referenced this issue from a commit

2026-10-29 23:19:06 +00:00