← Back to all runs
Build Run: 118d30b5 CodexCoder21Organization/PerformanceTestEmbedded
Stored run summary updated 329m 54s .
Projects performancetest.embedded:performancetest-embedded
Repository CodexCoder21Organization/PerformanceTestEmbeddedbranch fix/L218-history-read-failure commit dd6e1b23326c
Droplets (0 active, 1 total) Image: 245388985 · 2 vCPU
Status
FAILED
Dynamic-dispatch event-ingestion/dispatch loop on shard 0 failed for run '118d30b5': buildtest.embedded.DynamicCompletionIngestionException: Could not commit the dynamic test completion for run '118d30b5', shard 0, test 'CodexCoder21Organization-PerformanceTestEmbedded-dd6e1b23326c3fe6bbb92d8a0b0c727fe4c2bbed/tests/testClosedStartupCannotReconcile.kts', lease '36163dc2-2d5d-4ad7-8187-e67b8532bf35-118d30b5-7abf73d7-37fd-4e20-844f-0aa956e57c31-L0', attempt '36163dc2-2d5d-4ad7-8187-e67b8532bf35-118d30b5-7abf73d7-37fd-4e20-844f-0aa956e57c31-A3': 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 '118d30b5' could not complete.
Build Rules
1 built , 0 failed, 1 total
Tests
0 passed , 0 failed, 55 total
6 hours
spent waiting (pending)
Total duration from build request until completion: 381m 47s
Excluding the 375m 48s spent pending in the queue: 5m 59s 381m 47s pending: 375m 48s 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 375m 48s installing dependencies: 13.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: 1m 16s 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 48s 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: 1m 49s. 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 48s (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. 1m 49s (cpu time)module cache packaging, transfer and install: 2m 29s 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 29sunit tests: 11s 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. 11s (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: 375m 48s 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. installing dependencies: 13.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: 1m 16s 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 48s 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: 1m 49s. 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 29s 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: 11s 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 13.8s module cache packaging, transfer and install 2m 29s uploading project 1m 16s unit tests 11s · waiting for completed tests cpu build rules 1m 48s · 1m 49s cpu pending 375m 48s Total 381m 47s Module cache: Shard 0 packaged the module cache in 1m 21s
cpu time
waiting for completed tests
Build Rules 1 built , 0 failed, 1 total
Status Build Rule Duration Output Error PASSED performancetest.embedded.buildMaven (2 recorded executions) 75239ms 0 files, 0 B
Test Results 0 passed , 0 failed, 55 total
Status Project Test Duration Error Test results unavailable for this run (summary reports 55 tests, but per-test detail was not recorded).
log retained until 2026-10-29T20:26:41.359Z; removed under the runs-pool size policy.