Repository navigation
test(computers): a multi env's computer follows its gateway's clock end to end on the local backend - #647
Closed
williamloo-scale wants to merge 1 commit into
Closed
test(computers): a multi env's computer follows its gateway's clock end to end on the local backend#647williamloo-scale wants to merge 1 commit into
williamloo-scale wants to merge 1 commit into
Conversation
…nd to end on the local backend The clock follower test bundle's desktop (ubuntu-24.04, the reference driver and the clock app) deployed beside an MCP server. sync_env_clock arms the gateway about 6 months back, and the session's shell and Python read the gateway's time, read between two reads of the gateway's clock; then after a day's advance and a re-arm at 60x, each write acknowledged before it returns. The session user can't write the clock page or file, read the follower's config or stop the follower, and a follower killed as root is back for the next write. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Closing: superseded by #649, which puts ubuntu-24.04 computers on the gateway's clock from the base image, with core configuring the follower at deploy and after a reset. FD-5477's remaining arm-time work ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
An end-to-end test of a multi env's computer on its gateway's clock on the local backend (
tst/integration/computer/clock_follower_test.py,int_test_slow). It deploys a desktop (ubuntu-24.04, the reference driver and theclockapp) beside an MCP server, then checks:sync_env_clocksets the clock about 6 months back, and the arm takes under 30 s.dateand Python agree with the gateway's clock to within 0.5 s.How it was tested
pytest -m int_test_slow tst/integration/computer/clock_follower_test.pyon local Docker (arm64) with the local registry: passed. The run is about 5 minutes with an image build. The amd64 image builds but wasn't run.Stack: follower → sync → this → reset.
🤖 Generated with Claude Code