← Back to all runs

Build Run: e7c314f8

CodexCoder21Organization/AiCliHostSupervisorDaemonEmbedded

Stored run summary updated . Data age: 286m 35s.

Projectsaicli.hostsupervisor:daemon
RepositoryCodexCoder21Organization/AiCliHostSupervisorDaemonEmbeddedbranch r94-partial-conversation-change-milliscommit f105669dfd66
Droplets (0 active, 1 total)
Image: 245388985 · 2 vCPU
Status
FAILED
Dynamic-dispatch event-ingestion/dispatch loop on shard 0 failed for run 'e7c314f8': buildtest.embedded.DynamicCompletionIngestionException: Could not commit the dynamic test completion for run 'e7c314f8', shard 0, test 'CodexCoder21Organization-AiCliHostSupervisorDaemonEmbedded-f105669dfd666c110dc991836b11afc2829ace32/tests/testSpendHistoryBothHarnesses.kts', lease '36163dc2-2d5d-4ad7-8187-e67b8532bf35-e7c314f8-7d367aba-30f1-406b-9b21-9f901576fb13-L9', attempt '36163dc2-2d5d-4ad7-8187-e67b8532bf35-e7c314f8-7d367aba-30f1-406b-9b21-9f901576fb13-A40': buildtest.embedded.ExecutionDurationPublicationFailure: Execution-duration publication failed for '/root/buildtest-data' while publishing 3 queued events for runs [15b0fd1b, 666fedcb]: java.io.IOException: No space left on device. New publications are refused. Queued publication for run 'e7c314f8' could not complete.
Build Rules
2 built, 0 failed, 2 total
Tests
38 passed, 0 failed, 233 total
Requested
8 hours
spent waiting (pending)
Started
Total duration from build request until completion: 516m 23s Excluding the 500m 2s spent pending in the queue: 16m 21s516m 23spending: 500m 2s 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.pending500m 2sinstalling dependencies: 14.3s 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: 22.9s 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: 2m 24s 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: 3m 14s. 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.2m 24s (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.3m 14s (cpu time)module cache packaging, transfer and install: 3m 19s 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 19sunit tests: 9m 59s 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.9m 59s (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 1m 8s
test time
16m 20s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/AiCliHostSupervisorDaemonEmbedded/pull/42 Commit https://github.com/CodexCoder21Organization/AiCliHostSupervisorDaemonEmbedded/commit/f105669dfd666c110dc991836b11afc2829ace32 kotlin-build-ci-upload-request=accf9d3c-1435-4b5b-b452-95bfe2c46212 Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:24:49.487Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:24:50.674Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:24:51.922Z; removed under the runs-pool size policy.

Build Rules

2 built, 0 failed, 2 total
StatusBuild RuleDurationOutputError
PASSEDaicli.hostsupervisor.daemon.buildFatJar (2 recorded executions)96123ms0 files, 0 B
PASSEDaicli.hostsupervisor.daemon.buildMaven (2 recorded executions)94070ms0 files, 0 B

Test Results

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

Build Log

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