← Back to all runs

Build Run: 7df8dbee

CodexCoder21Organization/HandoffApi

Stored run summary updated . Data age: 2724m 21s.

The live projection feed is disconnected, has an unapplied gap, or has a reset that has not finished; this page shows the last committed stored summary.
Projectshandoff:api
RepositoryCodexCoder21Organization/HandoffApibranch scratch/api-red-2812commit f55771d74d2e
Droplets (0 active, 1 total)
buildtest-7df8dbee-a108b7fid 613855246 · s-2vcpu-4gb · 64.227.109.15069m 56s0s15m30m45m60m75m
Image: 245388985 · 2 vCPU
Status
FAILED
Provisioning deadline exceeded for runId=7df8dbee: elapsedMs=4285111 limitMs=600000 firstAdmissionAt=1793278555050 currentAttempt=5 createdDropletIds=[613855246] lastFailure=none
Tests
0 passed, 1 failed, 1 totalStored test results are still catching up.
Test ages
010-1s01-10s110-30s030-60s01-5m05-15m015-60m01h+0test lifespanpassedfailedrunning

1 test: 1 failed.

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
9 hours
spent waiting (pending)
Started
Total duration from build request until completion: 667m 16s Excluding the 593m 42s spent pending in the queue: 73m 34s667m 16spending: 593m 42s 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.pending593m 42sinstalling dependencies: 18s 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: 24.1s 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: 1m 49s 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: —. 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.1m 49s (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)module cache packaging, transfer and install: 1m 54s 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.1m 54sunit tests: 69m 8s 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: 400ms. 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.69m 8s (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.400ms (cpu time)
Module cache: Shard 0 packaged the module cache in 51.5s
test time
5.5s
cpu time
400ms
Finished
Notes
Branch: scratch/api-red-2812 Commit https://github.com/CodexCoder21Organization/HandoffApi/commit/f55771d74d2e594e1e2168279616f1a455e07e37 kotlin-build-ci-upload-request=79e90af0-83d7-4419-8ff3-ae21c256b3f1

Test Results

0 passed, 1 failed, 1 totalStored test results are still catching up.
StatusProjectTestDurationError
FAILEDhandoff.api.testtestStatusReportPageAcceptedLimitRoundTrips1705msjava.lang.AssertionError: A page accepted by the public constructor must round-trip through its own JSON parser; serialized 65764 bytes: Status report page exceeds the 65536-byte response limit. at handoff.api.test.TestStatusReportPageAcceptedLimitRoundTripsKt.testStatusReportPageAcceptedLimitRoundTrips(testStatusReportPageAcceptedLimitRoundTrips.kt:27) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at kompile.TestRunner.executeTest(TestRunner.kt:47) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at community.kotlin.kompile.testrunner.bootstrap.BootstrapRunner.main(BootstrapRunner.java:449) Caused by: java.lang.IllegalArgumentException: Status report page exceeds the 65536-byte response limit. at handoff.api.StatusReportPage$Companion.fromJson(StatusReportPage.kt:140) at handoff.api.test.TestStatusReportPageAcceptedLimitRoundTripsKt.testStatusReportPageAcceptedLimitRoundTrips(testStatusReportPageAcceptedLimitRoundTrips.kt:25) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at kompile.TestRunner.executeTest(TestRunner.kt:47) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at community.kotlin.kompile.testrunner.bootstrap.BootstrapRunner.main(BootstrapRunner.java:449)

Build Log

log retained until 2026-10-29T19:41:49.443Z; removed under the runs-pool size policy.