Builds the workspace and runs its assigned partition of the test suite.
Name
buildtest-c7fd8bbb-s3-a22991f
Droplet id
606765136
Role
test shard 3
State
destroyed
IP address
143.198.102.85
Size
s-2vcpu-4gb
Region
sfo3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
Lifetime
4m 19s
Utilization
all43.1%5m43.9%1m33.7%
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
6m 31s
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 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.
[shard 3/10] [2026-10-06 22:02:47] Droplet created: id=606765136, name=buildtest-c7fd8bbb-s3-a22991f
[shard 3/10] [2026-10-06 22:02:47] Droplet active at 143.198.102.85
[shard 3/10] [2026-10-06 22:03:18] ssh_key_grant_retry runId=c7fd8bbb shardIndex=3 dropletId=606765136 failedAttempt=1 maxAttempts=3 action=retry-same-droplet error=SandboxException: SJVM virtual method invocation timed out after 30s: dropletserviceserver/DropletServiceClientImpl.addSshKeyToDroplet(JLjava/lang/String;)V
[shard 3/10] [2026-10-06 22:03:48] ssh_key_grant_retry runId=c7fd8bbb shardIndex=3 dropletId=606765136 failedAttempt=2 maxAttempts=3 action=retry-same-droplet error=DropletServiceCallStalledException: Droplet service call addSshKeyToDroplet stalled for 30000ms while granting SSH access to droplet 606765136.
[shard 3/10] [2026-10-06 22:03:53] SSH access granted to droplet 606765136
[shard 3/10] [2026-10-06 22:03:53] Waiting for guest readiness on droplet 606765136
[shard 3/10] [2026-10-06 22:05:36] provisioning_failure runId=c7fd8bbb shardIndex=3 shardCount=10 method=awaitGuestReadiness attempt=1 maxAttempts=3 elapsedMs=301263 classification=INFRASTRUCTURE/PROVISIONING action=retrying error=GuestReadinessBudgetExceededException: Guest readiness for 143.198.102.85 did not complete within the existing provisioning budget of 102180 ms; elapsed=102183 ms. The allocation must be replaced before run work starts.
[shard 3/10] [2026-10-06 22:05:38] Waiting for failed droplet 606765136 deletion before retrying provisioning
[shard 3/10] [2026-10-06 22:07:13] provisioning_retry_backoff runId=c7fd8bbb shardIndex=3 method=awaitGuestReadiness completedAttempt=1 backoffMs=1000 classification=INFRASTRUCTURE/PROVISIONING
[shard 3/10] [2026-10-06 22:08:22] provisioning_failure runId=c7fd8bbb shardIndex=3 shardCount=10 method=createBuildDroplet attempt=2 maxAttempts=3 elapsedMs=467958 classification=INFRASTRUCTURE/PROVISIONING action=exhausted error=DropletServiceCallStalledException: Droplet creation outcome for 'buildtest-c7fd8bbb-s3-a2299c0' is not safe to retry inline because the async request result was not delivered conclusively. No per-droplet fleet polling was started; the coordinator must use its fleet-wide cleanup-before-requeue path. Last failure: SandboxException: Cannot invoke 'dropletserviceserver/DropletCreationStatusImpl.getRequestId()Ljava/lang/String;': the sandboxed connection was invalidated (a prior call 'dropletserviceserver/DropletServiceClientImpl.addSshKeyToDroplet(JLjava/lang/String;)V' timed out after 30s). Reopen the connection to use a fresh SJVM sandbox.
[shard 3/10] [2026-10-06 22:08:22] ERROR: Provisioning failed for runId=c7fd8bbb shardIndex=3 method=createBuildDroplet attempts=2/3 elapsedMs=467958 classification=INFRASTRUCTURE/PROVISIONING: Droplet creation outcome for 'buildtest-c7fd8bbb-s3-a2299c0' is not safe to retry inline because the async request result was not delivered conclusively. No per-droplet fleet polling was started; the coordinator must use its fleet-wide cleanup-before-requeue path. Last failure: SandboxException: Cannot invoke 'dropletserviceserver/DropletCreationStatusImpl.getRequestId()Ljava/lang/String;': the sandboxed connection was invalidated (a prior call 'dropletserviceserver/DropletServiceClientImpl.addSshKeyToDroplet(JLjava/lang/String;)V' timed out after 30s). Reopen the connection to use a fresh SJVM sandbox.