Gitea maps BOTH `action_run.status=2` (Failure) AND `status=3` (Cancelled) to commit-status string `"failure"`. On a busy `main` with `concurrency: cancel-in-progress: true`, every merge burst cancels prior in-flight runs (status=3) — those bubble to the combined-status `failure` rollup and inflate the watchdog's red%, generating phantom `[main-red]` issues (mc#1562/#1552/#1540/#1532/#1527/#1526/#1522/#1503/#1487/#1484). Per mc#1564 the cleanest filter at this layer is option B (description string): cancelled-run entries carry description `"Has been cancelled"`, real failures carry `"Failing after Ns"`. is_red() now excludes the former from the failed[] list, and combined=failure alone (no per-entry detail) only trips red when statuses[] is empty (the CI-emitter-direct edge case from render_body's existing fallback). Match is description == "Has been cancelled" exactly (after strip), not substring, so a hypothetical real-failure log line containing that phrase still counts as red. Canonical Gitea 1.22.6 enum per `models/actions/status.go`: 1=Success, 2=Failure, 3=Cancelled, 4=Skipped, 5=Waiting, 6=Running, 7=Blocked (reference: operator memory reference_gitea_action_status_enum_corrected_2026_05_19 + reference_chronic_red_sweep_cancelled_vs_failed_filter) Tests (6 new, all 36 in suite pass locally): - cancel-cascade entry alone → not red - real-failure entry alone → red (no over-filter) - mixed cancel + real → red, failed[] contains only real failures - all entries cancelled → not red (the phantom-issue case) - combined=failure + empty statuses[] → still red (preserve fallback) - exact-match contract (substring would over-match) Refs: - mc#1564 - mc#1529 (chronic-red triage that surfaced this) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.