Shard 0: builds the workspace, carries the run's build rule and artifact collection, and runs its share of the tests.
Name
buildtest-50ad57da-a75d1a7
Droplet id
606783509
Role
primary
State
destroyed
IP address
165.232.159.186
Size
s-2vcpu-4gb
Region
sfo3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
Lifetime
15m 45s
Utilization
all24.2%5m24.2%1m32.9%
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
3m 11s
installing dependencies
41.1s
uploading project
27.2s
build rules
12m 55s
Tests on this droplet
No test attempt has been attributed to this droplet. A run whose tests have not started yet, and a run whose coordinator recorded no droplet for its attempts, both look like this.
Build log from this droplet
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.
This droplet's share of the run's build log is still being read. The BuildTest WUI is still building its cached view of 'droplet-log:50ad57da:606783509:shard-0' (this data has not been materialized since the process started). The rebuild is running in the background and did not finish within 5000ms. Retry in a few seconds. Reload this page to show it, or download it.