Files
forgefirm/forgetest/tests
ScottW514 dc9bede034 forgetest: the first /state parses each suite module once
The first GET /state after forgetest starts hashes every test's
implementation, and it took from 81 s to more than 12 minutes on the
bench reference. Two causes:

- sibling_imports() read and parsed a test's module and every sibling it
  imports, transitively, once per test: 280 ast.parse calls for 26 suite
  modules. module_parts() kept its own parse, sibling_imports() kept
  none.
- The page gives up on a poll after 20 s and polls again; the server
  thread goes on computing. Each new poll started the same cold work
  beside the first, all of it on the one CPU, so the longer the first
  took the more copies ran. That is the spread between 81 s and 12
  minutes.

Each module's text and tree are now read and parsed once and kept, as
are its direct sibling imports, and the implementation hash is filled
by one thread at a time: a poll that arrives while it is computed waits
for it instead of repeating it. catalog.forget(path) drops what is kept
about a file, for the unit tests that edit their modules.

The hashes do not move: every test's implementation hash and domain
fingerprint on the image manifest of 20260923220034 is byte-identical
before and after, so no result is invalidated. On the host the cold
computation went from 7.00 s to 0.29 s (280 parses to 25). On the bench
reference (the file bind-mounted on image 20260923220034, the page
open) the first /state answered in 8 to 12 s after a restart, where the
same restart earlier in the evening had not answered after 7 minutes.

tests/test_responsiveness.py pins both: each suite module parsed at most
once while every test's implementation hash is computed, and three
threads reading one test's hash compute it once. With the old behavior
put back by a patch both fail (280 parses for 26 modules; the hash
computed 3 times). forgetest's unit tests 454 OK. forgetest is the
dev-only harness, outside the catalog's coverage; its catalog
consequence is none, since no fingerprint moves.
2026-09-23 19:22:10 -04:00
..
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 14:25:45 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00
2026-09-18 12:14:22 -04:00