← Back to all runs

Build Run: 7ecc07fe

CodexCoder21Organization/HandoffWui

Stored run summary updated . Data age: 304m 32s.

Projectshandoff:wui
RepositoryCodexCoder21Organization/HandoffWuibranch feature/fix/progressive-fleet-catalogcommit be2b597ca211
Droplets (0 active, 1 total)
buildtest-7ecc07fe-aa0332eid 613892768 · s-2vcpu-4gb · 143.244.184.13312m 24s4m 25s3m 1s13m 41s0s10m20m30m
Image: 245388985 · 2 vCPU
Status
FAILED
Dynamic-dispatch event-ingestion/dispatch loop on shard 0 failed for run '7ecc07fe': java.io.IOException: No space left on device
Build Rules
7 built, 0 failed, 7 total
Tests
37 passed, 277 failed, 317 total
Requested
6 hours
spent waiting (pending)
Started
Total duration from build request until completion: 449m 3s Excluding the 414m 55s spent pending in the queue: 34m 7s449m 3spending: 414m 55s 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.pending414m 55sinstalling dependencies: 24.7s 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: 8.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: 12m 26s 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: 22m 24s. 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.12m 26s (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.22m 24s (cpu time)module cache packaging, transfer and install: 7m 23s 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.7m 23sunit tests: 13m 44s 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.13m 44s (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)
Module cache: Shard 0 packaged the module cache in 4m 25s
test time
26m 37s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/HandoffWui/pull/43 Commit https://github.com/CodexCoder21Organization/HandoffWui/commit/be2b597ca211a32811b8f18ea7aaba146fb59b63 kotlin-build-ci-upload-request=85c223de-1286-4d4a-8661-730310132bda Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:34:31.803Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:34:32.517Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:34:33.743Z; removed under the runs-pool size policy.

Build Rules

7 built, 0 failed, 7 total
StatusBuild RuleDurationOutputError
PASSEDhandoff.wui.buildFatJar57910ms0 files, 0 B
PASSEDhandoff.wui.buildMaven (2 recorded executions)371261ms0 files, 0 B
PASSEDhandoff.wui.coldStartFatJarScenario396156ms0 files, 0 B
PASSEDhandoff.wui.inlineEditingBrowserScenario (2 recorded executions)173763ms0 files, 0 B
PASSEDhandoff.wui.persistedMainColdStartScenario217099ms0 files, 0 B
PASSEDhandoff.wui.settingsVersionSourceScenario30404ms0 files, 0 B
PASSEDhandoff.wui.transportDependencyPomScenario55422ms0 files, 0 B

Test Results

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

Build Log

log retained until 2026-10-29T20:34:32.517Z; removed under the runs-pool size policy.