← CodexCoder21Organization/UrlResolver FAILED

buildtest-9a5eaab4-s9-a24a1f1

Builds the workspace and runs its assigned partition of the test suite.
Name
buildtest-9a5eaab4-s9-a24a1f1
Droplet id
607196899
Role
test shard 9
State
destroyed
IP address
209.38.79.130
Size
s-2vcpu-4gb
Region
sfo3
Image
245388985
Hardware
2 vCPU
Created
Destroyed
Lifetime
3m 14s
Utilization
all18.4%5m50.2%1m42.8%
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-9a5eaab4-s9-a24a1f1id 607196899 · s-2vcpu-4gb · 209.38.79.1305m 51s0s1m2m3m4m5m
PhaseEnteredDuration
provisioning droplet5m 51s

Tests on this droplet

The per-test attempt history for build run '9a5eaab4' is still being read. The BuildTest WUI is still building its cached view of 'droplet-attempts:9a5eaab4' (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.

Build log from this droplet

The lines of the run's build log that this droplet wrote — the ones beginning with "[shard 9/", including the recovery lines the coordinator writes on its behalf as "[buildtest-coordinator] [shard 9/" — 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 9/10] [2026-10-08 06:17:45] Awaiting shard 0's workspace module cache preparation outcome before creating this follower's droplet
[shard 9/10] [2026-10-08 07:13:54] Droplet created: id=607196899, name=buildtest-9a5eaab4-s9-a24a1f1
[shard 9/10] [2026-10-08 07:13:54] Droplet active at 209.38.79.130
[shard 9/10] [2026-10-08 07:14:32] ssh_key_grant_retry runId=9a5eaab4 shardIndex=9 dropletId=607196899 failedAttempt=1 maxAttempts=3 action=retry-same-droplet error=DropletServiceCallStalledException: Droplet service call addSshKeyToDroplet stalled for 30000ms while granting SSH access to droplet 607196899.
[shard 9/10] [2026-10-08 07:14:56] SSH access granted to droplet 607196899
[shard 9/10] [2026-10-08 07:14:56] Waiting for guest readiness on droplet 607196899
[shard 9/10] [2026-10-08 07:16:21] provisioning_failure runId=9a5eaab4 shardIndex=9 shardCount=10 method=awaitGuestReadiness attempt=1 maxAttempts=3 elapsedMs=306126 classification=INFRASTRUCTURE/PROVISIONING action=retrying error=GuestReadinessBudgetExceededException: Guest readiness for 209.38.79.130 did not complete within the existing provisioning budget of 77656 ms; elapsed=77747 ms. The allocation must be replaced before run work starts.
[shard 9/10] [2026-10-08 07:16:24] Waiting for failed droplet 607196899 deletion before retrying provisioning
[shard 9/10] [2026-10-08 07:17:13] provisioning_retry_backoff runId=9a5eaab4 shardIndex=9 method=awaitGuestReadiness completedAttempt=1 backoffMs=1000 classification=INFRASTRUCTURE/PROVISIONING
[shard 9/10] [2026-10-08 07:20:24] Droplet created: id=607197951, name=buildtest-9a5eaab4-s9-a24a26b
[shard 9/10] [2026-10-08 07:20:24] Droplet active at 209.38.139.234
[shard 9/10] [2026-10-08 07:20:34] SSH access granted to droplet 607197951
[shard 9/10] [2026-10-08 07:20:35] Waiting for guest readiness on droplet 607197951