← ContainerNursery TESTING

buildtest-e204ecf8-aa32ba6

Shard 0: builds the workspace, carries the run's build rule and artifact collection, and runs its share of the tests.
Name
buildtest-e204ecf8-aa32ba6
Droplet id
610430380
Role
primary
State
alive
IP address
137.184.7.91
Size
s-2vcpu-4gb
Region
sfo3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
still alive
Lifetime
2093m 42s so far
Utilization
all32.1%5m46.8%1m100.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-e204ecf8-aa32ba6id 610430380 · s-2vcpu-4gb · 137.184.7.912085m 7s0s120m240m360m480m600m720m840m960m1080m1200m1320m1440m1560m1680m1800m1920m2040m
PhaseEnteredDuration
provisioning droplet1m 39s
installing dependencies9.4s
uploading project5s
build rules4m 37s
packaging module cache1m 45s
module cache ready, starting tests1m 31s
unit tests2085m 7s

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:e204ecf8:610430380: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.