Skip to content
Sign up

flagon-io/g1t

public
00

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

gitagentscloudflarerustforgemcp

Commit

FIRST_REPORT_MS says what lost Deploy #443's two jobs: a start cancelled with the request that made it, not a rollout

The runner's logs (scripts/ops/runner-errors.mjs, and the telemetry of the two jobs' sandboxes) show it: the start's RPC was cancelled at 00:13:03 while the containers library retried 'no container instance', and the start gave up at 00:13:14 with nobody left to tell. Neither job's container ever made a request.

G1t-Session:
ses_01m5b7dq37eb8tm6hbrkw3rt12
syntaqxcommitted Parent1cb0896Browse files
1 file+6−40/1 viewed
+6−4
8888
8989 /// How long a job on g1t's machines has to say anything after it starts.
9090 /// Its runner reports its first step within seconds (6 to 12 on Deploy
91−/// #445); one that has said nothing by now lost its sandbox before it ran
92−/// anything (on 2026-10-20, a runner rollout replacing containers under
93−/// two jobs of Deploy #443), so it is tried again rather than left until
94−/// SILENT_MS fails it.
91+/// #445); one that has said nothing by now never got a sandbox, so it is
92+/// tried again rather than left until SILENT_MS fails it. On 2026-10-20
93+/// two jobs of Deploy #443 were started from the request of a job that
94+/// reported its end: no container was free, the library's retries took
95+/// longer than that job's container stayed connected, and the start was
96+/// cancelled with the request, after the jobs were marked as running.
9597 pub const FIRST_REPORT_MS: u64 = 3 * 60 * 1000;
9698
9799 /// Whether a job that started at `started` and was last heard from at

Comments

Sign in to comment.