af89d3fcbd
Canary #2090 has been red for 6 consecutive runs over 4+ hours, all timing out at the TLS-readiness step exactly at the 10-min cap. Time window correlates with three CP commits that landed today/yesterday and changed EC2 boot behaviour: - molecule-controlplane@a3eb8be — fix(ec2): force fresh clone of /opt/adapter - molecule-controlplane@ed70405 — feat(sweep): wire up healthcheck loop - molecule-controlplane@4ab339e — fix(provisioner): aggregate cleanup errors Two changes here, both surgical: 1. Bump the bash-side TLS deadline from 600s to 900s, and the canvas TS mirror from 10m to 15m. Stays below the 20-min provision envelope (so a genuinely-stuck tenant still fails loud at the earlier provision step instead of masquerading as TLS). 2. On TLS-timeout, dump a diagnostic burst before exiting: - getent hosts $TENANT_HOST (DNS resolution state) - curl -kv $TENANT_URL/health (TLS handshake + HTTP layer) The previous failure log was just "no 2xx in N min" with no signal for which layer was actually broken. After this, the next timeout tells us whether DNS, TLS handshake, or HTTP layer is the culprit so the CP root cause can be isolated without speculation. This is the unblock; a separate molecule-controlplane issue tracks the underlying regression suspicion. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| e2e | ||
| README.md | ||
Tests
This repo uses the standard monorepo testing convention: unit tests live with their package, cross-component E2E tests live here.
Where to find tests
| Scope | Location |
|---|---|
| Go unit + integration (platform, CLI, handlers) | workspace-server/**/*_test.go — run with cd workspace-server && go test -race ./... |
| TypeScript unit (canvas components, hooks, store) | canvas/src/**/__tests__/ — run with cd canvas && npm test -- --run |
| TypeScript unit (MCP server handlers) | mcp-server/src/__tests__/ — run with cd mcp-server && npx jest |
| Python unit (workspace runtime, adapters) | workspace/tests/ — run with cd workspace && python3 -m pytest |
| Python unit (SDK: plugin + remote agent) | sdk/python/tests/ — run with cd sdk/python && python3 -m pytest |
| Cross-component E2E (spans platform + runtime + HTTP) | tests/e2e/ ← you are here |
Why split this way
- Go requires co-located
_test.gofiles to access unexported symbols. - Per-package test commands keep the inner loop fast — changing canvas doesn't re-run Go tests.
tests/e2e/covers scenarios that no single package owns: a full workspace lifecycle, A2A across two provisioned agents, delegation chains, bundle round-trips.
Running E2E
Every E2E script here assumes the platform is running at localhost:8080 and (where noted) provisioned agents are online. See the header comment of each .sh for specifics.
Cleaning up rogue test workspaces
If an E2E run aborts before its teardown runs (Ctrl-C, crash, CI timeout),
the platform can be left with workspaces whose config volume is stale or
empty — Docker's unless-stopped restart policy then spins those
containers in a FileNotFoundError loop. The platform's pre-flight check
(#17) marks such workspaces failed on the next restart, but a manual
cleanup is useful:
bash scripts/cleanup-rogue-workspaces.sh # deletes ws with id/name starting aaaaaaaa-, bbbbbbbb-, cccccccc-, test-ws-
MOLECULE_URL=http://host:8080 bash scripts/cleanup-rogue-workspaces.sh
The script DELETEs each matching workspace via the API and
force-removes the ws-<id[:12]> container as a belt-and-suspenders
fallback.