← Back to all runs

Build Run: 78027f97

CodexCoder21Organization/ContainerNursery

Stored run summary updated . Data age: 307m 36s.

Projectscontainernursery:container-nursery
RepositoryCodexCoder21Organization/ContainerNurserybranch wip/w6-184728-persistedcommit 127990849bc7
Droplets (0 active, 6 total)
Image: 245388985 · 2 vCPU
Status
FAILED
Could not persist build run '78027f97' to /root/buildtest-data/runs/78027f97/run.json after one quick retry; the in-memory run was made authoritative and transitioned to FAILED. Underlying failure: java.io.IOException: No space left on device
Build Rules
16 built, 1 failed, 17 total
Tests
125 passed, 1624 failed, 1749 total
Requested
8 minutes
spent waiting (pending)
Started
Total duration from build request until completion: 63m 36s Excluding the 8m 53s spent pending in the queue: 54m 43s63m 36spending: 8m 53s 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.pending8m 53sprovisioning droplet: 2m 1s 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: 17.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: 14.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 projectbuild rules: 11m 11s 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: 20m 55s. 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.11m 11s (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.20m 55s (cpu time)module cache packaging, transfer and install: 8m 23s 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.8m 23sunit tests: 32m 35s 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.32m 35s (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 2m 17s; shards 1, 4–6, 8 fetched and installed it in 1m 35s to 2m 37s
test time
82m 1s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/ContainerNursery/pull/787 Commit https://github.com/CodexCoder21Organization/ContainerNursery/commit/127990849bc72c471232bf4ad2e0873a5cf89abf kotlin-build-ci-upload-request=87815be9-bc6c-458a-b40d-fe1037aabfd7 Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T22:30:14.513Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T22:30:15.110Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T22:30:15.682Z; removed under the runs-pool size policy.

Build Rules

16 built, 1 failed, 17 total
StatusBuild RuleRepresentative wall timeOutputError
PASSEDcontainernursery.buildCertificateProcessDeathAfterCertificatePublicationFixture257249ms0 files, 0 B
PASSEDcontainernursery.buildCertificateProcessDeathAfterCompletionBeforeConfigCommitFixture43737ms0 files, 0 B
PASSEDcontainernursery.buildCertificateProcessDeathAfterConfigCommitBeforeCleanupFixture46839ms0 files, 0 B
PASSEDcontainernursery.buildCertificateProcessDeathAfterConfigCommitFixture276910ms0 files, 0 B
PASSEDcontainernursery.buildCertificateProcessDeathAfterPairPublicationFixture48042ms0 files, 0 B
PASSEDcontainernursery.buildCertificateProcessDeathBeforeCertificatePublicationFixture40033ms0 files, 0 B
PASSEDcontainernursery.buildFatJar (2 recorded executions)95486ms0 files, 0 B
PASSEDcontainernursery.buildHistoricalCleanupRecordWriter (2 recorded executions)21562ms0 files, 0 B
PASSEDcontainernursery.buildInheritedHttpsFixtures (2 recorded executions)31843ms0 files, 0 B
PASSEDcontainernursery.buildInheritedScenarioWrapper() (2 recorded executions)27592ms1 file, 7.1 KB
FAILEDcontainernursery.buildJarHistoryOwnerFixture() (2 recorded executions)7122ms0 files, 0 BBuild rule containernursery.buildJarHistoryOwnerFixture() started but its build did not report completion before the run ended with status FAILED
PASSEDcontainernursery.buildJarHistoryOwnerRecoveryScaleFixture32259ms0 files, 0 B
PASSEDcontainernursery.buildJarHistoryUnreapedActiveOwnerFixture59529ms0 files, 0 B
PASSEDcontainernursery.buildMaven (2 recorded executions)26142ms0 files, 0 B
PASSEDcontainernursery.buildOversizedStdoutFixture28440ms0 files, 0 B
PASSEDcontainernursery.buildPidStressGuardInputs (2 recorded executions)70647ms0 files, 0 B
PASSEDcontainernursery.buildSoakWorkerSlotDeclarations2576ms0 files, 0 B

Test Results

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

Build Log

log retained until 2026-10-29T22:30:15.110Z; removed under the runs-pool size policy.