b7f0b279eb
After #2710 + #2714 + the MOLECULE_STAGING_MINIMAX_API_KEY repo secret landed (2026-05-04 08:37Z), the next dispatched canary (run 25309323698) cleared every previous failure point but timed out at step 8/11 with `curl: (28) Operation timed out after 30002 ms`. The canary creates a fresh org per run, so every A2A POST hits a cold workspace + cold MiniMax endpoint: workspace boot → claude-code adapter starts event loop → first prompt ships → TLS handshake to api.minimax.io → cold model warmup → first-token generation Cold-call P95 lands around 25-30s on MiniMax-M2.7-highspeed; the 30-second `CURL_COMMON --max-time` is right on the edge and the run that timed out was 30.002s of zero bytes received. Fix: override `--max-time` for the canary's A2A POST only — 90s gives ~3x headroom. Subsequent A2A turns to the same workspace are sub-second, so this only widens step 8 of the canary's first turn. The shared CURL_COMMON timeout stays at 30s for everything else (provision, register, terminal, peers, teardown), where 30s is right. Verifies the rest of the canary script (provision, DNS, terminal-EIC, A2A round-trip) is platform-correct and the only operational gap is this latency knob. |
||
|---|---|---|
| .. | ||
| e2e | ||
| harness | ||
| ops | ||
| 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.