Repository navigation
feat: add host-owned test runner for supervisors - #137
Merged
Merged
Conversation
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.
Integration tests that start a Codex sandbox can fail when launched inside an agent's existing sandbox. Add a host-owned test runner so the root supervisor can request configured suites through
gestalt_test_runner, with Mobile owning their processes and results.docs/host-tests.md.The runner is disabled by default. Deployment and operator configuration are required to activate it. Candidate fingerprints exclude ignored dependencies/toolchains, and before/after checks do not detect edits reverted during execution. Host execution grants the test code the host user's filesystem authority.
Validation:
npm run format:check,npm run license:check,npm run check,npm run lint, andnpm run buildpassed.npm test: 2,747 passed, 2 skipped.PLAYWRIGHT_BROWSERS_PATH=... npm run test:e2e: 302 passed.The first browser run encountered worktree dependency symlink/client-build failures; after correcting that setup, the failed subset and final full suite passed. This does not claim the previously blocked manager/Serena suite has been rerun on a deployed host.