← Back to all runs

Build Run: 9fec490a

CodexCoder21Organization/PerformanceTestServerService

Stored run summary updated . Data age: 295m 1s.

Projectsperformancetest.server:performancetest-server-service
RepositoryCodexCoder21Organization/PerformanceTestServerServicebranch fix/L215-bind-before-reconciliationcommit f6e9b2f3a30a
Droplets (0 active, 1 total)
Image: 245388985 · 2 vCPU
Status
COMPLETED
Build Rules
5 built, 0 failed, 5 total
Tests
28 passed, 0 failed, 28 total
0%50%100%Tests passedTests failedTests canceled before they reached a verdictTests started and still runningTests started (including the ones still running)Tests finished, whether they passed or notTests passed or failed, excluding the ones canceledTests passedpassedfailedrunning02m 21s
Test ages
05101520250-1s21-10s2310-30s330-60s01-5m05-15m015-60m01h+0test lifespanpassedfailedrunning

28 tests: 28 passed.

Lane activity

Lane activity cannot be drawn for this run: this run's per-test attempt history could not be read this time. The coordinator did not return a complete attempt-history response. Reload this page in a minute to try again. Every other chart on this page is unaffected.

Requested
7 hours
spent waiting (pending)
Started
Total duration from build request until completion: 454m 54s Excluding the 448m 52s spent pending in the queue: 6m 1s454m 54spending: 448m 52s 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.pending448m 52sprovisioning droplet: 1m 23s 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: 8.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: 532ms 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 3s 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: 2m 27s. 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 3s (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.2m 27s (cpu time)unit tests: 2m 24s 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: 49.9s. 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.2m 24s (wall clock)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.49.9s (cpu time)collecting results: 1s 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: 25ms 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
49.9s
Finished
Notes
PR https://github.com/CodexCoder21Organization/PerformanceTestServerService/pull/25 Commit https://github.com/CodexCoder21Organization/PerformanceTestServerService/commit/f6e9b2f3a30a9c7cd76388175c7c3a305ea043b4 kotlin-build-ci-upload-request=ffdfcae9-e303-4e01-bc6a-897a34a18d94 Retention: archive.tar.gz: archive.tar.gz retained until 2026-10-29T20:04:02.093Z; removed under the runs-pool size policy. Retention: build.log: log retained until 2026-10-29T20:04:02.336Z; removed under the runs-pool size policy. Retention: test-events.jsonl: test-events.jsonl retained until 2026-10-29T20:04:02.382Z; removed under the runs-pool size policy.

Build Rules

5 built, 0 failed, 5 total
StatusBuild RuleDurationOutputError
PASSEDperformancetest.server.buildClientMaven()754ms7 files, 1.7 MB
PASSEDperformancetest.server.buildClientResourcesJar()474ms1 file, 1.6 MB
PASSEDperformancetest.server.buildFatJar()113889ms1 file, 59.9 MB
PASSEDperformancetest.server.buildMaven()880ms80 files, 42.4 MB
PASSEDperformancetest.server:performancetest-server-client:0.0.131635ms7 files, 1.7 MB

Test Results

28 passed, 0 failed, 28 total
StatusProjectTestDurationError
PASSEDperformancetest.serverbytecodeGeneratorClassNameExistsInServedJar942ms
PASSEDperformancetest.servere2eSandboxedClientCoRunRoundTrip20027ms
PASSEDperformancetest.serverrpcBoundedHistoryQueriesPreserveCompleteCounts2731ms
PASSEDperformancetest.serverrpcBytecodeRequestServesClientJar7718ms
PASSEDperformancetest.serverrpcBytecodeRequestWithoutJarsExplainsMiswiring3087ms
PASSEDperformancetest.serverrpcChunkUploadsAcceptRawByteArrays16429ms
PASSEDperformancetest.serverrpcCoRunFlowSubmitsAndReadsBack2604ms
PASSEDperformancetest.serverrpcGetHistogramReturnsRealBuckets3085ms
PASSEDperformancetest.serverrpcGetMissingRunReturnsFoundFalse5739ms
PASSEDperformancetest.serverrpcGetStatisticsReturnsRealStatsAfterSubmit2863ms
PASSEDperformancetest.serverrpcHealthReturnsOK1278ms
PASSEDperformancetest.serverrpcListPaginatedReturnsExpectedShape2653ms
PASSEDperformancetest.serverrpcSubmitReturnsRunMap2402ms
PASSEDperformancetest.serverrpcUnknownMethodThrows2336ms
PASSEDperformancetest.servertestAllHostedEndpointsStayGatedDuringHistoryLoad4215ms
PASSEDperformancetest.servertestBundledTransportMatchesQualifiedReleases1752ms
PASSEDperformancetest.servertestClientPreservesApi004CoRunUploadSessionDescriptor823ms
PASSEDperformancetest.servertestCloseCanReenterFromStartupReadWithoutPublishingService8926ms
PASSEDperformancetest.servertestCloseReleasesHeldHistorySource6632ms
PASSEDperformancetest.servertestCloseReportsFullClosedError5845ms
PASSEDperformancetest.servertestClosedStartupCannotOverwriteNewOwnerRecord9021ms
PASSEDperformancetest.servertestHistoryReadFailureCannotReturnCompletePartialPage6223ms
PASSEDperformancetest.servertestHostedLogStreamsSurviveStartupInitialization9223ms
PASSEDperformancetest.servertestHostedRequestsKeepBoundedLogging6921ms
PASSEDperformancetest.servertestInitializationFailureIsVisibleAndCanRetry5432ms
PASSEDperformancetest.servertestListenerReadyWhileDropletCleanupReplyIsHeld20644ms
PASSEDperformancetest.servertestListenerReadyWhilePersistedReadIsHeld9205ms
PASSEDperformancetest.servertestStartupReconciliationUsesOrchestratorMode1499ms

Build Log

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