corbie check [--tag <tag>]… [--wait 90s]
start one small run, and report which part of a setup did not respond
Run it last when you set anything up. It starts a run with one script job and one timer, and prints four lines, each with a status and the time it took. It fails unless every line is ok.
the controller took the start ok 0.6s a runner took the job ok 0.3s the controller took the result ok 0.4s the timer fired ok 41.0s
okit happened
lateit took more than 20s: on a serverless host, the bucket did not call the function and the once-a-minute call did the work
neverit did not happen within --wait
A line that is not ok is followed by its causes, on a computer and on a serverless host. The timer is never late: on a serverless host it waits for the once-a-minute call. While the command waits, it prints what it waits for.
The check reads only the store, so it is the same wherever Corbie runs.
--tag <tag>send the job to a runner that has the tag; repeatable; by default any runner takes it
--wait <time>how long to wait for each line, from the one before it; default 90s
- Functions the calls a serverless host must make
Every command takes --json, --config and --store: see corbie --help.