test(deploy): word the long-watch checks for any watch length
CI / verify (pull_request) Successful in 52s
CI / infrastructure-smoke (pull_request) Successful in 21s
CI / migration-smoke (pull_request) Successful in 1m48s
CI / image-build (pull_request) Successful in 18s
CI / deploy-smoke (same-origin) (pull_request) Successful in 41s
CI / deploy-smoke (split) (pull_request) Successful in 59s
CI / verify (pull_request) Successful in 52s
CI / infrastructure-smoke (pull_request) Successful in 21s
CI / migration-smoke (pull_request) Successful in 1m48s
CI / image-build (pull_request) Successful in 18s
CI / deploy-smoke (same-origin) (pull_request) Successful in 41s
CI / deploy-smoke (split) (pull_request) Successful in 59s
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]>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
ff8a3e8097
commit
f50e8f4201
@@ -924,9 +924,9 @@ async function run() {
|
|||||||
);
|
);
|
||||||
check(
|
check(
|
||||||
result.tally.get("recycle").offline === 0,
|
result.tally.get("recycle").offline === 0,
|
||||||
"the display stayed live across the realtime recycle",
|
`the display stayed live for the whole ${recycleWatchMs / 1000}s watch${recycleWatchMs > 300_000 ? ", across a realtime recycle" : ""}`,
|
||||||
);
|
);
|
||||||
check(page.sessionRequests.length === 1, "the realtime recycle did not remount the display");
|
check(page.sessionRequests.length === 1, "the display was never remounted during the watch");
|
||||||
await page.close();
|
await page.close();
|
||||||
kiosk.close();
|
kiosk.close();
|
||||||
await finishOwner(owner);
|
await finishOwner(owner);
|
||||||
|
|||||||
Reference in New Issue
Block a user