← Back to all runs
Build Run: 4bff852d CodexCoder21Organization/AiCliHostSupervisorDaemonEmbedded
Stored run summary updated 315m 49s .
Projects aicli.hostsupervisor:daemon
Repository CodexCoder21Organization/AiCliHostSupervisorDaemonEmbeddedbranch r94-partial-conversation-change-millis commit 96845d34ea7a
Droplets (0 active, 1 total) Image: 245388985 · 2 vCPU
Status
FAILED
Build watchdog detected that run '4bff852d' has been in PENDING status for 429 minutes, which exceeds the maximum allowed build duration of 180 minutes. The build appears to be hung and has been marked as FAILED.
Build Rules
2 built , 0 failed, 2 total
Tests
0 passed , 202 failed , 202 total
2 hours
spent waiting (pending)
Total duration from build request until completion: 570m 57s
Excluding the 130m 36s spent pending in the queue: 440m 21s 570m 57s pending: 130m 36s 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. pending 130m 36s provisioning droplet: 435m 48s 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 droplet 435m 48s installing dependencies: 10.8s 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 dependencies uploading project: 18.6s 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 project build rules: 1m 47s 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 17s. 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 rules 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. 1m 47s (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 17s (cpu time)module cache packaging, transfer and install: 2m 10s 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 install 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. 2m 10sunit tests: 5.9s 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 tests 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. 5.9s (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)pending: 130m 36s 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. provisioning droplet: 435m 48s 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. installing dependencies: 10.8s 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. uploading project: 18.6s 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. build rules: 1m 47s 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 17s. 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. module cache packaging, transfer and install: 2m 10s 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. unit tests: 5.9s 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. installing dependencies 10.8s module cache packaging, transfer and install 2m 10s uploading project 18.6s unit tests 5.9s · waiting for completed tests cpu build rules 1m 47s · 3m 17s cpu pending 130m 36s provisioning droplet 435m 48s Total 570m 57s Module cache: Shard 0 packaged the module cache in 1m 2s
cpu time
waiting for completed tests
Build Rules 2 built , 0 failed, 2 total
Status Build Rule Duration Output Error PASSED aicli.hostsupervisor.daemon.buildFatJar 81792ms 0 files, 0 B PASSED aicli.hostsupervisor.daemon.buildMaven (2 recorded executions) 79897ms 0 files, 0 B
Test Results 0 passed , 202 failed , 202 total
Status Project Test Duration Error Test results unavailable for this run (summary reports 202 tests, but per-test detail was not recorded).
log retained until 2026-10-29T19:28:31.242Z; removed under the runs-pool size policy.