← Back to all runs

Build Run: a4395125

CodexCoder21Organization/PerformanceTestServerService

Stored run summary updated . Data age: 297m 50s.

Projectsperformancetest.server:performancetest-server-service
RepositoryCodexCoder21Organization/PerformanceTestServerServicebranch fix/L215-bind-before-reconciliationcommit 5a2db17c9628
Droplets (0 active, 1 total)
buildtest-a4395125-aa03330id 613892914 · s-2vcpu-4gb · 64.23.189.1201m 54s3m 22s6m 55s0s5m10m
Image: 245388985 · 2 vCPU
Status
FAILED
Dynamic-dispatch event-ingestion/dispatch loop on shard 0 failed for run 'a4395125': buildtest.embedded.DynamicCompletionIngestionException: Could not commit the dynamic test completion for run 'a4395125', shard 0, test 'CodexCoder21Organization-PerformanceTestServerService-5a2db17c9628cfeb1134f93289fcffb4bb86e59d/tests/testInitializationFailureIsVisibleAndCanRetry.kts', lease '36163dc2-2d5d-4ad7-8187-e67b8532bf35-a4395125-c2d8b850-8af9-4785-a0c3-4781d63a6822-L4', attempt '36163dc2-2d5d-4ad7-8187-e67b8532bf35-a4395125-c2d8b850-8af9-4785-a0c3-4781d63a6822-A21': 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 'a4395125' could not complete.
Build Rules
2 built, 1 failed, 1 pending, 4 total
Tests
25 passed, 0 failed, 36 total
Requested
6 hours
spent waiting (pending)
Started
Total duration from build request until completion: 376m Excluding the 363m 1s spent pending in the queue: 12m 58s376mpending: 363m 1s 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.pending363m 1sprovisioning droplet: 1m 54s 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: 12.1s 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: 33.2s 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: 3m 22s 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: 5m 21s. 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.3m 22s (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.5m 21s (cpu time)unit tests: 6m 55s 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.6m 55s (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
6m 47s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/PerformanceTestServerService/pull/25 Commit https://github.com/CodexCoder21Organization/PerformanceTestServerService/commit/5a2db17c9628cfeb1134f93289fcffb4bb86e59d kotlin-build-ci-upload-request=880aab32-5b26-40c7-a736-fe7950a97af3 Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:23:51.637Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:23:51.940Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:23:52.060Z; removed under the runs-pool size policy.

Build Rules

2 built, 1 failed, 1 pending, 4 total
StatusBuild RuleDurationOutputError
PENDINGperformancetest.server.buildClientMaven()-0 files, 0 B
PASSEDperformancetest.server.buildClientResourcesJar()405ms1 file, 1.6 MB
PASSEDperformancetest.server.buildMaven()2401ms80 files, 42.4 MB
FAILEDperformancetest.server.buildServerVerificationResourcesJar()318782ms0 files, 0 BBuild rule performancetest.server.buildServerVerificationResourcesJar() started but its build did not report completion before the run ended with status FAILED

Test Results

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

Build Log

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