UrlResolver PR https://github.com/CodexCoder21Organization/UrlResolver/pull/774 had two

Reported (UTC): 2026-07-14 13:39

UrlResolver PR https://github.com/CodexCoder21Organization/UrlResolver/pull/774 had two consecutive kotlin.build remote failures unrelated to its deep-map/SJVM change. First run https://buildtest.kotlin.build/run?id=993c8d94 passed 1090/1102: nine failures were 0ms non-executions after three 60-second Coursier unified-classpath/workspace-local-artifact resolution timeouts, while three existing network-discovery tests flaked (including a 507ms mean against a 500ms threshold). Rerun https://buildtest.kotlin.build/run?id=23f6d1ca passed 1097/1102: two different tests again failed at 0ms from the same three-attempt Coursier timeout; testActiveQueryDoesNotResurrectWithdrawnService repeated its provider-discovery empty-result assertion; testRelayByteArrayParamEdgeSizes reported the expected service in Known services while still failing its announcement condition; testStressPeerExchangeRaceCondition had 1/5 clients miss discovery. The PR target passed remotely and bld-build passed; a local isolated full-suite run passed these networking tests. Impact: unrelated dependency/network flakes consume roughly an hour per rerun and block otherwise-green PRs. Suggested durable fixes: prewarm each shard Coursier cache or share the build artifact dependency graph so tests do not independently resolve it over the network; separately add reliable high-amplification reproducers and fix the active-query/peer-discovery races rather than relying on reruns.

Production verification — 2026-07-17

Status: STILL EXISTS. Live GitHub verification found 1 referenced tracker(s) still open: https://github.com/CodexCoder21Organization/UrlResolver/pull/774. A live ProductionHealth connection also emitted repeated NothingToCompleteException gossip failures, while the stopped HardwareControlFabric daemon log ends with Netty ByteBuf leak reports.

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.