BuildTest - Droplet buildtest-efae5080-s3-a0055fa

buildtest-efae5080-s3-a0055fa

Builds the workspace and runs its assigned partition of the test suite.

Name

buildtest-efae5080-s3-a0055fa

Droplet id

606691012

Role

test shard 3

State

destroyed

IP address

164.92.70.51

Size

s-2vcpu-4gb

Region

sfo3

Image

245388985

Hardware

2 vCPU

Created

Destroyed

Lifetime

14m 38s

Utilization

all110.8%5m550.0%1m550.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

Phase	Entered	Duration
provisioning droplet		1m 56s
installing dependencies		16.2s
uploading project		15.1s
build rules		4m 42s
unit tests		9m 5s

Phase

Entered

Duration

provisioning droplet

1m 56s

installing dependencies

16.2s

uploading project

15.1s

build rules

4m 42s

unit tests

9m 5s

Tests on this droplet

14 test attempts, 14 passed, 0 failed. They occupied 11m 55s 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 14m 38s.

Test	Attempt	Status	Duration
foundation.url.resolver / stressTestRelayFailoverDebugCapture	1	PASSED	1m 30s
foundation.url.resolver / stressTestRelayFailoverToAlternateRelayWhenRegisteredRelayDies	1	PASSED	1m 30s
foundation.url.resolver / stressTestHealthySameTierRelayWinsUnderContention	1	PASSED	1m
foundation.url.resolver / stressTestBytecodeFetchAggregatesRelayFailureDetailsUnderConcurrentCalls	1	PASSED	1m 13s
foundation.url.resolver / testNetlabUploadUnrelatedMissingPathKeepsEnvironment	1	PASSED	1m 11s
foundation.url.resolver / testLiveProjectionResilienceNegativeControlDifferentIdentityNeverRecovers	1	PASSED	47.1s
foundation.url.resolver / testRequestBytecodeViaRelayAttachesResourcePathMetadata	1	PASSED	1m 13s
foundation.url.resolver / testRegistrationMultiaddressesNeverEmptyAfterReannounce	1	PASSED	1m 14s
foundation.url.resolver / testFailedSandboxCreationDoesNotLeakSjvmOrPersistentRpcThreads	1	PASSED	17.2s
foundation.url.resolver / stressTestGossipRetentionStaysWithinByteBudgetOnStalledPeerPopulation	1	PASSED	16.2s
foundation.url.resolver / testServiceProviderRestartWithNewPeerIdDiscoveredByHealthMonitor	1	PASSED	18.2s
foundation.url.resolver / testCircuitBreakerFastPruneAfterThreeFailures	1	PASSED	21.9s
foundation.url.resolver / stressTestRequestBytecodeFromServiceWaitsForServiceDiscovery	2	PASSED	35.9s
foundation.url.resolver / stressTestOnPeerRegisteredWithRelayObservationBeforeRegistry	2	PASSED	25.1s

Test

Attempt

Status

Started

Ended

Duration

foundation.url.resolver / stressTestRelayFailoverDebugCapture

PASSED

1m 30s

foundation.url.resolver / stressTestRelayFailoverToAlternateRelayWhenRegisteredRelayDies

PASSED

1m 30s

foundation.url.resolver / stressTestHealthySameTierRelayWinsUnderContention

PASSED

foundation.url.resolver / stressTestBytecodeFetchAggregatesRelayFailureDetailsUnderConcurrentCalls

PASSED

1m 13s

foundation.url.resolver / testNetlabUploadUnrelatedMissingPathKeepsEnvironment

PASSED

1m 11s

foundation.url.resolver / testLiveProjectionResilienceNegativeControlDifferentIdentityNeverRecovers

PASSED

47.1s

foundation.url.resolver / testRequestBytecodeViaRelayAttachesResourcePathMetadata

PASSED

1m 13s

foundation.url.resolver / testRegistrationMultiaddressesNeverEmptyAfterReannounce

PASSED

1m 14s

foundation.url.resolver / testFailedSandboxCreationDoesNotLeakSjvmOrPersistentRpcThreads

PASSED

17.2s

foundation.url.resolver / stressTestGossipRetentionStaysWithinByteBudgetOnStalledPeerPopulation

PASSED

16.2s

foundation.url.resolver / testServiceProviderRestartWithNewPeerIdDiscoveredByHealthMonitor

PASSED

18.2s

foundation.url.resolver / testCircuitBreakerFastPruneAfterThreeFailures

PASSED

21.9s

foundation.url.resolver / stressTestRequestBytecodeFromServiceWaitsForServiceDiscovery

PASSED

35.9s

foundation.url.resolver / stressTestOnPeerRegisteredWithRelayObservationBeforeRegistry

PASSED

25.1s

Build log from this droplet

The lines of the run's build log that this droplet wrote — the ones beginning with "[shard 3/", including the recovery lines the coordinator writes on its behalf as "[buildtest-coordinator] [shard 3/" — 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:efae5080:606691012:shard-3' (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.