← Back to all runs

Build Run: 7c2cc037

CodexCoder21Organization/DigitalOceanDropletServiceServer

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

Projectsdropletserviceserver:droplet-service-server
RepositoryCodexCoder21Organization/DigitalOceanDropletServiceServerbranch gh-readonly-queue/main/pr-181-faffe6b27a305a4f0f0c1789664a5c5bf07accaecommit a587c0ea09e7
Droplets (0 active, 4 total)
buildtest-7c2cc037-ab8c876id 611538554 · s-2vcpu-4gb · 161.35.230.2247m 20s1m 57s16m 43sbuildtest-7c2cc037-s1-ab8c8f0id 611542011 · s-2vcpu-4gb · 143.244.184.1422m 38s3m 16s11m 28sbuildtest-7c2cc037-s2-ab8c8f1id 611542000 · s-2vcpu-4gb · 64.23.251.6815m 23sbuildtest-7c2cc037-s4-ab8c8ecid 611542010 · s-2vcpu-4gb · 137.184.10.462m 16s2m 19s12m 34s0s5m10m15m20m25m
Image: 245388985 · 2 vCPU
Status
FAILED
2 test(s) failed
Build Rules
7 built, 0 failed, 7 total
Tests
657 passed, 2 failed, 659 total
Requested
1 minute
spent waiting (pending)
Started
Total duration from build request until completion: 30m 35s Excluding the 1m 22s spent pending in the queue: 29m 13s30m 35spending: 1m 22s 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.pendingprovisioning droplet: 1m 36s 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 dropletinstalling 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.4s 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: 7m 20s 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: 12m 3s. 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.7m 20s (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.12m 3s (cpu time)module cache packaging, transfer and install: 3m 5s 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 5sunit tests: 16m 17s 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 17s (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: 33.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.3s 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 1m 8s; shards 1, 2, 4 fetched and installed it in 37.4s to 55s
test time
63m 51s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/DigitalOceanDropletServiceServer/pull/181 Commit https://github.com/CodexCoder21Organization/DigitalOceanDropletServiceServer/commit/a587c0ea09e79100e343204693b858fc301532b3 kotlin-build-ci-upload-request=120aec04-3bbc-4cb6-9a56-e53916761579 Dynamic dispatch degradation: 5 failed-test re-lease(s) within the run; 2 test(s) exhausted their failure budget (see dispatch_decision events for details) Dynamic dispatch: 6 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:14.054Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-22T12:29:14.358Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-22T12:29:14.728Z; removed under the runs-pool size policy.

Build Rules

7 built, 0 failed, 7 total
StatusBuild RuleRepresentative wall timeOutputError
PASSEDdropletserviceserver.buildClientResourcesJar (2 recorded executions)148291ms0 files, 0 B
PASSEDdropletserviceserver.buildFleetOverviewReadsMaven (2 recorded executions)29543ms0 files, 0 B
PASSEDdropletserviceserver.buildInMemoryProviderTestSupport (2 recorded executions)59560ms0 files, 0 B
PASSEDdropletserviceserver.buildInvariantFinalMaven (2 recorded executions)239513ms0 files, 0 B
PASSEDdropletserviceserver.buildMaven (2 recorded executions)88789ms0 files, 0 B
PASSEDdropletserviceserver.buildWebCronConnectionCarrierTestSupport90735ms0 files, 0 B
PASSEDdropletserviceserver:droplet-service-client:0.0.2462222ms8 files, 1.9 MB

Test Results

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

Build Log

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