← board

testmgr: FPC benchmark comparison + static web dashboard (bench, suites, FPC conformance)

Why

The bench tier ([[feature-testmgr-opt-tier-and-benchmarks]]) tracks pxx timings across -O0/-O2/-O3 per SHA, and the idle chain (full → opt → bench, once per SHA, repo-idle) already runs it "when all other work is done, every so often." But:

  1. No external baseline. Timings are pxx-vs-pxx. The user wants a comparison against FPC (3.2.2 on the box) — is our -O2/-O3 code competitive with the reference compiler? That's the meaningful number.
  2. Nothing is visible. twatch_web.py shows live run + regressions + report links only. No bench history, no test-suite pass rates, no FPC-conformance breakdown. The user wants a web page for all of it, click-through, viewable without the daemon.
  3. FPC conformance is opaque. run_pascal_conformance.sh prints pass/fail/ skip/auto-gated counts to a log; pxx.skip has 237 freeform-reason entries. No structured output, no distinction between "genuine gap" and "tests FPC internals we intentionally differ on — will never pass", no per-category view. FPC-suite burndown is deprioritized ([[task-pascal-conformance-long-tail]] prio 12) but the user still wants the RESULTS surfaced.

What

Delivery decisions (user, 2026-07-11): static committed HTML (generated into tstate/, viewable from git like BOARD.html, no daemon needed); taxonomy built now, agentic per-test review of FPC tests deferred to a follow-up.

1. --bench: FPC comparison column

2. pxx.skip: reason-tag taxonomy

3. run_pascal_conformance.sh --json <path>

4. Static web dashboard (tools/twatch_web.py --static --out <dir>)

5. Wire into twatch idle chain

Gates / notes

Log