While running the complete BuildTestEmbedded suite with 'scripts/test.bash --test .' on branch

Reported (UTC): 2026-07-14 03:10

While running the complete BuildTestEmbedded suite with 'scripts/test.bash --test .' on branch fix/deterministic-admission-crash-recovery at commit 03316d6, kompile-cli 0.0.65's JVM test-runner controller emitted two result-channel failures: first 'java.io.StreamCorruptedException: invalid type code: 73' at community.kotlin.kompile.testrunner.jvm.TcpCommunicationHandler.handleCommunication(JvmUnitTestLauncher.kt:333), then 'java.lang.ClassNotFoundException: buildtest.embedded.BuildCancelledException' from ObjectInputStream.resolveClass at the same handler while deserializing a child-JVM result. The suite continued but finished 529/531 with two test failures, so these channel errors make the authoritative relationship between child test failures and controller results uncertain and dump hundreds of thousands of tokens of warnings/errors. Focused target and adjacent invocations were unaffected. Suggested durable fix: frame each TCP result message so concurrent/partial writes cannot corrupt ObjectInputStream boundaries, and deserialize test exceptions through a classloader containing the selected test's compiled artifact (or transmit a classloader-independent failure DTO containing type/message/stack) rather than requiring application exception classes on the controller classpath.

Production verification — 2026-07-17

Status: STILL EXISTS. Current production remains degraded rather than retired: buildtest.kotlin.build returned HTTP 200 but took 8.89 seconds, while the production host showed load average 60.59, CPU pressure near 90%, and the BuildTest JVM at about 1.8 GiB RSS.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.