Production motion audit observes long main-thread tasks #74

New issue

Open

opened 2026-10-07 09:43:46 +00:00 by kayg · 1 comment

kayg commented

2026-10-07 09:43:46 +00:00

Owner

During issue #55’s scripts/verify latency run on infraternal-dev (x86_64, 8 cores; tracer-browser phase load 17.73 10.48 10.96; 300 ms RTT ±30 ms), apps/tracer/test/motion-audit.spec.ts failed its no-long-tasks assertion at line 599. The production browser reported two main-thread self tasks of 63 ms and 62 ms during the keyboard theme interaction; the test expected an empty list. This was measured by the existing 4x CPU production-build audit. The full profile log and failure context are in #55.

During issue #55’s `scripts/verify latency` run on infraternal-dev (x86_64, 8 cores; tracer-browser phase load 17.73 10.48 10.96; 300 ms RTT ±30 ms), `apps/tracer/test/motion-audit.spec.ts` failed its no-long-tasks assertion at line 599. The production browser reported two main-thread `self` tasks of 63 ms and 62 ms during the keyboard theme interaction; the test expected an empty list. This was measured by the existing 4x CPU production-build audit. The full profile log and failure context are in #55.

kayg referenced this issue

2026-10-07 10:32:58 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

kayg commented

2026-10-07 10:32:58 +00:00

Author

Owner

Latest 4x CPU production motion audit did not produce an in-progress pointer-checkbox sample: pointerTickMidOffset was 0 (computed offset 0px) and the assertion expecting a value above 0 failed at apps/tracer/test/motion-audit.spec.ts:477. The checkbox was checked; the sampled frame had already reached zero. The run also captured the production setup/recovery screenshots under apps/tracer/test-results/motion-audit-measure-deplo-2b97c--capture-production-screens/attachments/. This run could not provide a fresh long-task duration because the motion assertion stopped the audit first. Full profile log was $HOME/.cache/codex-scratch/latency-gate/latency-final.log.

Latest 4x CPU production motion audit did not produce an in-progress pointer-checkbox sample: `pointerTickMidOffset` was 0 (computed offset `0px`) and the assertion expecting a value above 0 failed at `apps/tracer/test/motion-audit.spec.ts:477`. The checkbox was checked; the sampled frame had already reached zero. The run also captured the production setup/recovery screenshots under `apps/tracer/test-results/motion-audit-measure-deplo-2b97c--capture-production-screens/attachments/`. This run could not provide a fresh long-task duration because the motion assertion stopped the audit first. Full profile log was `$HOME/.cache/codex-scratch/latency-gate/latency-final.log`.

kayg referenced this issue

2026-10-07 10:55:40 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

kayg referenced this issue from a commit

2026-10-10 09:20:35 +00:00

Merge latency-gate: 300 ms RTT test profile and input-to-photon gate (#55, D130)

kayg referenced this issue

2026-10-28 17:52:29 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

~~kayg referenced this issue 2026-10-28 17:53:55 +00:00~~

Orchestrator handover 2026-10-28: moving to a new machine #254

~~kayg referenced this issue 2026-10-28 17:53:56 +00:00~~