← CodexCoder21Organization/UrlResolver FAILED

buildtest-5a6e2d0e-s6-ac4bea4

Builds the workspace and runs its assigned partition of the test suite.
Name
buildtest-5a6e2d0e-s6-ac4bea4
Droplet id
607029881
Role
test shard 6
State
destroyed
IP address
64.225.58.93
Size
s-2vcpu-4gb
Region
nyc3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
Lifetime
3m 5s
Utilization
all35.0%5m15.3%1m6.6%
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-5a6e2d0e-s6-ac4bea4id 607029881 · s-2vcpu-4gb · 64.225.58.938m 45s0s2m4m6m8m
PhaseEnteredDuration
provisioning droplet8m 45s

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 6/", including the recovery lines the coordinator writes on its behalf as "[buildtest-coordinator] [shard 6/" — kept verbatim. Coordinator lines that name no shard belong to the run rather than to any one droplet and are not included.
Download this droplet's full log
[shard 6/10] [2026-10-07 18:11:21] Droplet created: id=607029881, name=buildtest-5a6e2d0e-s6-ac4bea4
[shard 6/10] [2026-10-07 18:11:21] Droplet active at 64.225.58.93
[shard 6/10] [2026-10-07 18:11:31] provisioning_failure runId=5a6e2d0e shardIndex=6 shardCount=10 method=addSshKeyToDroplet attempt=1 maxAttempts=3 elapsedMs=356033 classification=INFRASTRUCTURE/PROVISIONING action=retrying error=GuestReadinessBudgetExceededException: Guest readiness for 64.225.58.93 did not complete within the existing provisioning budget of 300000 ms; elapsed=351652 ms. The allocation must be replaced before run work starts.
[shard 6/10] [2026-10-07 18:11:42] Waiting for failed droplet 607029881 deletion before retrying provisioning
[shard 6/10] [2026-10-07 18:14:29] Waiting for droplet capacity before retrying failed boot; refreshing admission in 30s
[shard 6/10] [2026-10-07 18:14:59] Waiting for droplet capacity before retrying failed boot; refreshing admission in 60s
[shard 6/10] [2026-10-07 18:15:59] Waiting for droplet capacity before retrying failed boot; refreshing admission in 120s
[shard 6/10] [2026-10-07 18:17:59] Waiting for droplet capacity before retrying failed boot; refreshing admission in 240s
[shard 6/10] [2026-10-07 18:21:59] Waiting for droplet capacity before retrying failed boot; refreshing admission in 300s
[shard 6/10] [2026-10-07 18:23:05] provisioning_retry_backoff runId=5a6e2d0e shardIndex=6 method=addSshKeyToDroplet completedAttempt=1 backoffMs=1000 classification=INFRASTRUCTURE/PROVISIONING
[shard 6/10] [2026-10-07 18:23:23] provisioning_failure runId=5a6e2d0e shardIndex=6 shardCount=10 method=createBuildDroplet attempt=2 maxAttempts=3 elapsedMs=1067688 classification=INFRASTRUCTURE/PROVISIONING action=exhausted error=DropletServiceCallStalledException: Droplet creation outcome for 'buildtest-5a6e2d0e-s6-ac4beeb' 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 6/10] [2026-10-07 18:23:24] ERROR: Provisioning failed for runId=5a6e2d0e shardIndex=6 method=createBuildDroplet attempts=2/3 elapsedMs=1067688 classification=INFRASTRUCTURE/PROVISIONING: Droplet creation outcome for 'buildtest-5a6e2d0e-s6-ac4beeb' 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.