Zayin/Ekklesia
3
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Projects Releases 8 Wiki Activity

test(deploy): opt-in display-device scenarios for the split smoke #56

Merged
Zayin_Admin merged 2 commits from test/m0-display-device-repro into main 2026-10-06 00:24:47 +00:00
Conversation 1 Commits 2 Files Changed 2
+1066
2 Commits
Author SHA1 Message Date
ekklesiaandClaude Opus 5.5 f50e8f4201 test(deploy): word the long-watch checks for any watch length
CI / verify (pull_request) Successful in 52s
Details
CI / infrastructure-smoke (pull_request) Successful in 21s
Details
CI / migration-smoke (pull_request) Successful in 1m48s
Details
CI / image-build (pull_request) Successful in 18s
Details
CI / deploy-smoke (same-origin) (pull_request) Successful in 41s
Details
CI / deploy-smoke (split) (pull_request) Successful in 59s
Details 
The recycle step's checks spoke of "the realtime recycle" even when
run with a watch shorter than the five-minute connection age, as module
CI does. They now say what they check: live for the whole watch (plus
"across a realtime recycle" when the watch is long enough), and never
remounted.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-05 19:09:51 -05:00
ekklesiaandClaude Opus 5.5 ff8a3e8097 test(deploy): add opt-in display-device scenarios to the split smoke
CI / verify (pull_request) Successful in 53s
Details
CI / infrastructure-smoke (pull_request) Successful in 13s
Details
CI / migration-smoke (pull_request) Successful in 1m48s
Details
CI / image-build (pull_request) Successful in 20s
Details
CI / deploy-smoke (same-origin) (pull_request) Successful in 48s
Details
CI / deploy-smoke (split) (pull_request) Successful in 55s
Details 
Reproduction harness for what the first production Signage deployment
found. With EKKLESIA_SMOKE_DISPLAY_DEVICE=1, the split smoke starts a
second headless Chromium (the "kiosk") whose profile directory is a
Docker volume. It pairs that kiosk through the real flow, closes it
cleanly, restarts it on the same profile, and then runs injected-failure
scenarios: two pages on one credential, a connectivity blip, one refused
viewer-session request, one refused realtime connection, a cross-origin
image-caching probe, a full realtime recycle, and revocation.

Every DevTools command and page-side request has its own deadline, and
each step has a budget. A step that overruns prints the exact call it
was waiting for. The proxy's "aborting with incomplete response" lines
are listed afterwards by UTC time and path only.

Off by default: several scenarios expect Signage and fail on today's
v0.1.1, by design.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-05 18:25:12 -05:00