Skip to content

[test] providers: stabilize capability discovery browser clock - #412

Draft
wangtiance wants to merge 1 commit into
ThinkFlowLab:mainfrom
wangtiance:codex/fix-nightly-capability-clock
Draft

wangtiance wants to merge 1 commit into
ThinkFlowLab:mainfrom
wangtiance:codex/fix-nightly-capability-clock

Conversation

@wangtiance

@wangtiance wangtiance commented Nov 20, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

The production browser lane in nightly run 44645615189 failed when capability discovery called pauseAt(new Date()) with a target already behind the running browser clock.

Pause with transport headroom, then realign the paused wall clock with the HTTP fixture before requesting each short-lived observation. Move the second pause before the paused-service response so advancing time cannot expire the observation being inspected. Keep the bilingual and explicit expiry assertions, and record the failure evidence in the development lessons.

Validation

  • Complete capability discovery script passed twice against a production preview and isolated assistant fixture using Playwright Core 1.58.2 and Windows Edge (Chromium); includes bilingual states, pause expiry, fixture generation and immutable history.

  • Production build, browser manifest, browser locale, i18n, JavaScript syntax and diff checks passed.

  • Browser runs preceded the latest main fast-forward; Linux Chromium CI remains to be verified.

  • Whole-PR pre-commit could not complete: after fixing local cache permissions, actionlint dependency downloads from proxy.golang.org timed out. This is an environment failure, not a passing validation.

## summary

- Pause the browser clock with transport headroom and align its wall
  time with the HTTP fixture before requesting capability observations.
- Freeze before the paused-service reply to preserve its expiry checks
  and bilingual presentations.
- Record the nightly failure evidence and clock-control lesson.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant