Shard 0: builds the workspace, carries the run's build rule and artifact collection, and runs its share of the tests.
Name
buildtest-207253fa-a13705f
Droplet id
606818435
Role
primary
State
destroyed
IP address
164.90.147.109
Size
s-2vcpu-4gb
Region
sfo3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
Lifetime
18m 20s
Utilization
all25.7%5m67.8%1m71.6%
This figure is the coordinator's measurement for the WHOLE RUN, across every droplet it held. There is no per-droplet utilization measurement; the tests timeline below is this droplet's own answer to the same question.
Phase timeline
Phase
Entered
Duration
provisioning droplet
1m 37s
installing dependencies
11.5s
uploading project
11s
build rules
3m 37s
unit tests
13m 50s
Tests on this droplet
9 test attempts, 8 passed, 0 failed, 1 canceled. They occupied 14m 50s of test time in total (attempts run several at a time on one droplet, so this can exceed the wall clock), while the droplet was held for 18m 20s.
The lines of the run's build log that this droplet wrote — the ones beginning with "[shard 0/", including the recovery lines the coordinator writes on its behalf as "[buildtest-coordinator] [shard 0/" — kept verbatim. Coordinator lines that name no shard belong to the run rather than to any one droplet and are not included.
[shard 0/10] [dispatch] Shard 0 pipeline failed, but provider liveness for droplet 606818435 was ALIVE; no dead-droplet requeue was requested. Original failure: java.lang.IllegalStateException: SSH session is not connected. Call connect() first.
[shard 0/10] [2026-10-07 02:55:20] ERROR: SSH session is not connected. Call connect() first.