← Back to all runs

Build Run: 4f082cba

CodexCoder21Organization/PerformanceTestEmbedded

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

Projectsperformancetest.embedded:performancetest-embedded
RepositoryCodexCoder21Organization/PerformanceTestEmbeddedbranch support/L215-persisted-read-filesystemcommit 5f67e938957a
Droplets (0 active, 1 total)
buildtest-4f082cba-aa032daid 613888712 · s-2vcpu-4gb · 24.199.126.842m 36s27m 19s0s10m20m30m
Image: 245388985 · 2 vCPU
Status
COMPLETED
Build Rules
1 built, 0 failed, 1 total
Tests
48 passed, 0 failed, 48 total
Requested
6 hours
spent waiting (pending)
Started
Total duration from build request until completion: 411m 15s Excluding the 403m 29s spent pending in the queue: 7m 46s411m 15spending: 403m 29s 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.pending403m 29sprovisioning droplet: 1m 46s 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.7s 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: 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: 2m 29s 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: 899ms. 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 29s (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.899ms (cpu time)unit tests: 3m 14s 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.3m 14s (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.5s 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: 1s 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
3.1s
cpu time
waiting for completed tests
Finished
Notes
PR https://github.com/CodexCoder21Organization/PerformanceTestEmbedded/pull/25 Commit https://github.com/CodexCoder21Organization/PerformanceTestEmbedded/commit/5f67e938957a509b505fb370732fadae4cdf01b9 kotlin-build-ci-upload-request=32e589fe-2d20-42db-b837-ba6f752089a3 Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:10:51.011Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:10:51.440Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:10:51.619Z; removed under the runs-pool size policy.

Build Rules

1 built, 0 failed, 1 total
StatusBuild RuleDurationOutputError
PASSEDperformancetest.embedded.buildMaven()899ms12 files, 3.1 MB

Test Results

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

Build Log

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