← Back to all runs

Build Run: 992447c3

CodexCoder21Organization/Photobooks

Stored run summary updated . Data age: 346m 7s.

Projectsphotobooks
RepositoryCodexCoder21Organization/Photobooksbranch chore/bld-build-gatecommit 16c69c3c9a13
Droplets (0 active, 1 total)
buildtest-992447c3-aa03335id 613894555 · s-2vcpu-4gb · 164.90.144.642m 55s1m 51s2m 4s0s2m4m6m
Image: 245388985 · 2 vCPU
Status
FAILED
Dynamic-dispatch event-ingestion/dispatch loop on shard 0 failed for run '992447c3': buildtest.embedded.DynamicCompletionIngestionException: Could not commit the dynamic test completion for run '992447c3', shard 0, test 'CodexCoder21Organization-Photobooks-16c69c3c9a131ab2f696829a134a40871e3e7c9d/tests/testBookPageImagesMatchPageOneSize.kts', lease '36163dc2-2d5d-4ad7-8187-e67b8532bf35-992447c3-00bcabda-78dd-485d-b385-a53b34e396d8-L0', attempt '36163dc2-2d5d-4ad7-8187-e67b8532bf35-992447c3-00bcabda-78dd-485d-b385-a53b34e396d8-A1': 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 '992447c3' could not complete.
Tests
0 passed, 0 failed, 5 total
Requested
6 hours
spent waiting (pending)
Started
Total duration from build request until completion: 371m 24s Excluding the 364m 22s spent pending in the queue: 7m 2s371m 24spending: 364m 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.pending364m 22sprovisioning droplet: 2m 55s 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: 7.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 dependenciesuploading project: 1m 47s 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 8s wall clock. Lifecycle time: the real elapsed time the run spent in the build rules 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 build rule finished while the run remained in the phase. CPU time: —. 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 rulesLifecycle time: the real elapsed time the run spent in the build rules 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 build rule finished while the run remained in the phase.2m 8s (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.— (cpu time)unit tests: 3s 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.3s (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)
test time
3m 19s
cpu time
waiting for completed tests
Finished
Notes
Branch: chore/bld-build-gate Commit https://github.com/CodexCoder21Organization/Photobooks/commit/16c69c3c9a131ab2f696829a134a40871e3e7c9d kotlin-build-ci-upload-request=49f26542-b5ff-4115-8531-999fcae70af5 Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:16:27.245Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:16:27.525Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:16:27.715Z; removed under the runs-pool size policy.

Test Results

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

Build Log

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