You're offline — showing cached data

MC board execution regression (Canary)

canary-board-regression
2026-06-13 06:13:52 SAST
← Back to Tasks

OVERRIDES runtime profile: uses direct_mixed (node Canary CLI + python mc_ticket.py) because the task runs a browser-driven QA battery, not the claude CLI — no AI model/provider is invoked, so the wrapper would inject the wrong env.

Daily execution regression for the Mission Control board v2 UI. Runs the Canary battery (tests/canary/run_board_battery.py) which drives every interactive board control in a real headless browser and asserts the OUTCOME (request fired / navigation / state change), not just that it renders.

Why this exists

Rendering / Tessa passes check "does it show?" and miss dead-control regressions. On 2026-06-08 htmx.trigger(el,'load') (a no-op in htmx 2.x after initial load) silently broke board search, every filter, sort, the mine pill, SSE live-refresh, quick-actions, and new-ticket-create — all firing zero requests with no console error, invisible to rendering tests. This gate exercises the controls so that class of bug fails CI instead of reaching Elmar.

What it catches

Overhead

One run ≈ 60–90s: creates one [CANARY-TEST] fixture (assigned elmar, project=test), spins a headless Chromium via the Canary daemon, runs ~12 checks, cleans up the fixture. self_heal: false keeps deterministic canary failures visible instead of spending the scheduler timeout on automated repair attempts. notify_on: failure → Telegram only when a control is dead. Exit non-zero on any failed check or console error.

Logs

Daily at 03:3030 3 * * *
Yes
shell
360s
No
in 21h (2026-06-14 03:30)

Task Definition

tasks/canary-board-regression.md
shell
set
No
No
python3 /home/lucienne/workspace/mission-control/tests/canary/run_board_battery.py

Edit Schedule

Result:
6
Runs (7d)
4
Completed
1
Failed
1
Timeout
67%
Success (7d)
1.5m
Avg Duration
infrastructure mc monitoring ui

Run History (6)

StartedFinishedStatusDurationOutputLog
3h ago 3h ago completed 39s
PROGRESS: creating canary fixture attempt 1/4 PROGRESS: created canary fixture MC-5055 PROGRESS: starting Canary browser ...
View log
1d ago 1d ago completed 38s
PROGRESS: creating canary fixture attempt 1/4 PROGRESS: created canary fixture MC-5008 PROGRESS: starting Canary browser ...
View log
2d ago 2d ago completed 39s
PROGRESS: creating canary fixture attempt 1/4 PROGRESS: created canary fixture MC-4943 PROGRESS: starting Canary browser ...
View log
3d ago 3d ago failed
[FAIL] mobile-vertical-scroll mobile board is not vertically scrollable: maxScroll=0
39s
[FAIL] mobile-vertical-scroll mobile board is not vertically scrollable: maxScroll=0
View log
4d ago 4d ago completed 35s
PROGRESS: creating canary fixture attempt 1/4 PROGRESS: created canary fixture MC-4855 PROGRESS: starting Canary browser ...
View log
4d ago 4d ago timeout
Killed after 360s --- partial stdout (last 0 chars) --- --- partial stderr (last 0 chars) ---
6.0m
Killed after 360s --- partial stdout (last 0 chars) --- --- partial stderr (last 0 chars) ---
View log

Comments (0)

No comments yet — add instructions for Luci
Help