← Back to all runs

Build Run: 8fa4ddf0

CodexCoder21Organization/Photobooks

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

Projectsphotobooks
RepositoryCodexCoder21Organization/Photobooksbranch gh-readonly-queue/main/pr-3-0a2eb8c7486e80a22e7d3fae19919451dbc7ffd2commit fd6215ddcb86
Droplets (0 active, 1 total)
buildtest-8fa4ddf0-aa0336did 613899163 · s-2vcpu-4gb · 144.126.217.151m 31s30.7s2m 40s0s1m2m3m4m
Image: 245388985 · 2 vCPU
Status
COMPLETED
Tests
5 passed, 0 failed, 5 total
Requested
5 hours
spent waiting (pending)
Started
Total duration from build request until completion: 328m 24s Excluding the 325m 45s spent pending in the queue: 2m 38s328m 24spending: 325m 45s 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.pending325m 45sprovisioning droplet: 1m 31s 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: 9.5s 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: 223ms 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: 28.9s 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.28.9s (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: 25.5s 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.25.5s (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)collecting results: 2.7s wall clock. Lifecycle time: the real elapsed time the run spent in the collecting results 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.collecting resultsfinishing: 173ms wall clock. Lifecycle time: the real elapsed time the run spent in the finishing 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.finishing
test time
—
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/Photobooks/pull/3 Commit https://github.com/CodexCoder21Organization/Photobooks/commit/fd6215ddcb8692c2b9795344afdaedeb2d065b85 kotlin-build-ci-upload-request=159875f5-625d-4c78-87e4-3d7cb82c6c4e Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:28:29.648Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:28:29.769Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:28:29.925Z; removed under the runs-pool size policy.

Test Results

5 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:28:29.769Z; removed under the runs-pool size policy.