You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] nightly: capability discovery browser test can pause its clock in the past #411
Scheduled Nightly 44645615189, browser-production tested main 7dc1152ba78bdec05db8d2bbeed4d347ca40b082 (attempt 1). Thirteen of fourteen browser journeys passed. capability_discovery.mjs:517 exited with clock.pauseAt: Error: Cannot fast-forward to the past, before the stale/future/legacy/connection assertions. Captured browser diagnostics had no page errors. Environment: GitHub-hosted Ubuntu 22.04.5, Node 24.22.1, Playwright Core 1.58.2 with Chromium headless shell, Vite production preview and isolated fixture (no live provider).
Reproduce
Use the browser-production setup, then run node tests/browser/capability_discovery.mjs. In the draft service check, after the partial-capability state, the test installs its browser clock and immediately asks it to pause at the Node process's current wall clock. The failure depends on timing; one local pass does not rule it out.
Expected: freeze browser time and verify the same service observation in both locales without a second request. Actual: Playwright refuses to pause at the supplied timestamp and the observation checks never run.
Scope and acceptance
Current main still has these calls. The stack is in Playwright's clock controller, not the product service. The likely race is that the browser clock ticks past the timestamp before the pause applies. Set an explicit installed time and a later pause target within that controlled clock, or use an equivalent deterministic setup. Keep fixture timestamps consistent with the controlled clock, preserve the bilingual/no-extra-request assertions, and verify multiple runs of the production-browser case. No independent rerun or product regression is claimed.
Activity