← CodexCoder21Organization/UrlProtocol FAILED

buildtest-e4a2d0aa-aa33ea1

Shard 0: builds the workspace, carries the run's build rule and artifact collection, and runs its share of the tests.
Name
buildtest-e4a2d0aa-aa33ea1
Droplet id
610628099
Role
primary
State
destroyed
IP address
164.92.64.198
Size
s-2vcpu-4gb
Region
sfo3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
Lifetime
53m 59s
Utilization
all16.5%5m2.7%1m0.0%
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

buildtest-e4a2d0aa-aa33ea1id 610628099 · s-2vcpu-4gb · 164.92.64.1987m 50s9m 5s34m 24s0s10m20m30m40m50m
PhaseEnteredDuration
provisioning droplet2m 18s
installing dependencies13.5s
uploading project15.1s
build rules7m 50s
packaging module cache1m 18s
module cache ready, starting tests9m 5s
unit tests34m 24s

Tests on this droplet

Per-test attempt history is not available from this coordinator, so this page cannot show which tests ran on this droplet. Everything else on the page is unaffected.

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:e4a2d0aa:610628099: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.