← Back to all runs

Build Run: 1bbc84f0

CodexCoder21Organization/DigitalOceanDropletServiceServer

Stored run summary updated . Data age: 283m 26s.

Projectsdropletserviceserver:droplet-service-server
RepositoryCodexCoder21Organization/DigitalOceanDropletServiceServerbranch fix/f5c-route-history-coveragecommit ea6384f4282c
Droplets (0 active, 10 total)
buildtest-1bbc84f0-ab8c90did 611543345 · s-2vcpu-4gb · 146.190.39.2122m 2s6m 27s2m 59s18m 21sbuildtest-1bbc84f0-s1-ab8c940id 611545747 · s-2vcpu-4gb · 137.184.188.872m 33s15m 4sbuildtest-1bbc84f0-s2-ab8c939id 611545669 · s-2vcpu-4gb3m 35sbuildtest-1bbc84f0-s3-ab8c93eid 611545742 · s-2vcpu-4gb · 64.23.169.1613m 21sbuildtest-1bbc84f0-s4-ab8c93cid 611545737 · s-2vcpu-4gb · 64.227.102.1243m 35sbuildtest-1bbc84f0-s5-ab8c937id 611545665 · s-2vcpu-4gb · 143.198.232.83m 28sbuildtest-1bbc84f0-s6-ab8c93aid 611545672 · s-2vcpu-4gb · 164.90.159.1162m 26s2m 8s14m 48sbuildtest-1bbc84f0-s7-ab8c93fid 611545735 · s-2vcpu-4gb · 165.232.151.1773m 45sbuildtest-1bbc84f0-s8-ab8c93bid 611545693 · s-2vcpu-4gb · 164.92.88.872m 42s2m 32s13m 39sbuildtest-1bbc84f0-s9-ab8c936id 611545664 · s-2vcpu-4gb · 134.199.213.1942m 45s14m 22s0s10m20m30m
Image: 245388985 · 2 vCPU
Status
FAILED
3 test(s) failed
Build Rules
7 built, 0 failed, 7 total
Tests
635 passed, 3 failed, 638 total
Requested
8 minutes
spent waiting (pending)
Started
Total duration from build request until completion: 45m 40s Excluding the 8m 1s spent pending in the queue: 37m 39s45m 40spending: 8m 1s wall clock. Queue time: the real elapsed time from run creation until the first recorded phase began. This is time the run waited before execution started.pending8m 1sprovisioning droplet: 9m 21s wall clock. Lifecycle time: the real elapsed time the run spent in the provisioning droplet phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress.provisioning droplet9m 21sinstalling dependencies: 11.1s wall clock. Lifecycle time: the real elapsed time the run spent in the installing dependencies phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress.installing dependenciesuploading project: 7.3s wall clock. Lifecycle time: the real elapsed time the run spent in the uploading project phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress.uploading projectbuild rules: 6m 30s wall clock. Build rules time: from the first droplet starting build rules until shard 0 finished the last one. The module cache packaging, transfer and install that follow are shown as their own stage. CPU time: 13m 13s. CPU time: the sum of all measured individual build rules CPU times. Because build rules run in parallel across multiple cores and droplets, this is normally larger than the wall-clock elapsed time.build rulesBuild rules time: from the first droplet starting build rules until shard 0 finished the last one. The module cache packaging, transfer and install that follow are shown as their own stage.6m 30s (wall clock)CPU time: the sum of all measured individual build rules CPU times. Because build rules run in parallel across multiple cores and droplets, this is normally larger than the wall-clock elapsed time.13m 13s (cpu time)module cache packaging, transfer and install: 3m 52s wall clock. Module cache time: from the last build rule finishing until the first test started. Shard 0 packages the workspace module cache it built and serves it; the other droplets fetch and install it. If the run is still in this stage, the span ends at the current render time.module cache packaging,transfer and installModule cache time: from the last build rule finishing until the first test started. Shard 0 packages the workspace module cache it built and serves it; the other droplets fetch and install it. If the run is still in this stage, the span ends at the current render time.3m 52sunit tests: 16m 31s wall clock. Lifecycle time: the real elapsed time the run spent in the unit tests phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress. This includes work after the last test finished, such as dispatching @PerformanceTest tests to the performance-test service. CPU time: unavailable because no tests have completed yet. CPU time: the sum of all measured individual tests CPU times. Because tests run in parallel across multiple cores and droplets, this is normally larger than the wall-clock elapsed time.unit testsLifecycle time: the real elapsed time the run spent in the unit tests phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress. This includes work after the last test finished, such as dispatching @PerformanceTest tests to the performance-test service.16m 31s (wall clock)CPU time: unavailable because no tests have completed yet. CPU time: the sum of all measured individual tests CPU times. Because tests run in parallel across multiple cores and droplets, this is normally larger than the wall-clock elapsed time.waiting for completed tests (cpu time)collecting results: 1m 3s wall clock. Lifecycle time: the real elapsed time the run spent in the collecting results phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress.collecting resultsfinishing: 1.9s wall clock. Lifecycle time: the real elapsed time the run spent in the finishing phase, from entering it until the next recorded phase began. If it is the final phase, the span ends at run completion or the current render time while the run is in progress.finishing
Module cache: Shard 0 packaged the module cache in 54.2s; shards 1, 6, 8, 9 fetched and installed it in 38s to 53.9s
test time
53m 37s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/DigitalOceanDropletServiceServer/pull/181 Commit https://github.com/CodexCoder21Organization/DigitalOceanDropletServiceServer/commit/ea6384f4282c59144d0a26d49a70c3e797e121cc kotlin-build-ci-upload-request=c6a572d5-803f-4f6e-b17b-fa0c96ffbfb2 Dynamic dispatch degradation: 7 failed-test re-lease(s) within the run; 3 test(s) exhausted their failure budget (see dispatch_decision events for details) Dynamic dispatch: 5 shard(s) did not finish provisioning; the run continued on the surviving shards. Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-22T12:29:54.575Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-22T12:29:54.904Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-22T12:29:55.590Z; removed under the runs-pool size policy.

Build Rules

7 built, 0 failed, 7 total
StatusBuild RuleRepresentative wall timeOutputError
PASSEDdropletserviceserver.buildClientResourcesJar (2 recorded executions)151385ms0 files, 0 B
PASSEDdropletserviceserver.buildFleetOverviewReadsMaven() (2 recorded executions)25626ms78 files, 42.4 MB
PASSEDdropletserviceserver.buildInMemoryProviderTestSupport (2 recorded executions)70828ms0 files, 0 B
PASSEDdropletserviceserver.buildInvariantFinalMaven (2 recorded executions)271099ms0 files, 0 B
PASSEDdropletserviceserver.buildMaven (2 recorded executions)18153ms0 files, 0 B
PASSEDdropletserviceserver.buildWebCronConnectionCarrierTestSupport71341ms0 files, 0 B
PASSEDdropletserviceserver:droplet-service-client:0.0.24163436ms8 files, 1.9 MB

Test Results

635 passed, 3 failed, 638 total
StatusProjectTestDurationError
Test results unavailable for this run (summary reports 638 tests, but per-test detail was not recorded).

Build Log

log retained until 2026-10-22T12:29:54.904Z; removed under the runs-pool size policy.