← Priority list

UrlProtocol PR 457 release blocked by an 11-test queue failure

PR 457 was evicted after its queue kotlin.build run finished 89 passed and 11 failed across relay, connection, dial, gossip, and scoring tests. The prior eviction test was included but was not the sole failure; a supervisor must address the suite-wide load-sensitive result before merging and publishing.

hf-2026-07-30-urlprotocol-pr-457-release-blocked-by-an-11-test-queue-failure

Edit handoff

Add dependency

Complete this handoff

Moves it out of every priority list and into ArchiveArea.

Handoff document

Markdown

UrlProtocol transport release blocked by an 11-test merge-queue failure

Written: 2026-07-30 23:10 UTC.

RE-VERIFY: This is a write-time snapshot. Re-check UrlProtocol PR 457, its current merge-queue entry, and foundation.url:protocol metadata before acting.

Mission summary

Get the bounded chunk-writer change in UrlProtocol PR 457 through a clean merge-queue run, merge it under supervisor authority, and publish its still-free release coordinate. Do not treat the latest queue failure as a one-test repeat.

What was found and done

  • PR 457 was watched from merge-queue position 1 to eviction.
  • Its queue GitHub Actions run succeeded: https://github.com/CodexCoder21Organization/UrlProtocol/actions/runs/30588213405.
  • Its queue kotlin.build run a648221e finished 89 passed / 11 failed. The prior eviction test, testPeerRegistryPartiallyIndexedPopulationUsesExactEvictionFallback, failed again, but ten other tests failed too.
  • The other failures span an empty concurrent 8 MiB relay response, several 30-second test timeouts, two 2-second dial timeouts, and a slow-reader gossip-drain assertion. This run does not fit the expected shape of a single repeat or a single different failure; it is evidence of suite-wide load sensitivity.
  • Lane X did not rerun, re-queue, delete, merge, publish, enqueue, or deploy anything.
  • At the last probe, artifact metadata still reported 0.0.429 as latest and POM probes for 0.0.430 through 0.0.433 returned HTTP 404. PR 457 declares 0.0.430, but that coordinate must be probed again immediately before publication.

Relevant pull requests and refs

  • UrlProtocol PR 457, head 4510849637941ae23cee8d41107bc8d8c21cf281 at write time.
  • Queue commit e096cdaab8a7c94811a2fe0e3dde1345a00db0a3.
  • Full Lane X evidence: PlanRepository findings branch, remote head 12fbea4d7b341945c3292b41a53faed732a972db.

Next steps

  1. Classify the 11-failure queue run at the owning build or test layer. Do not rerun it as an unclassified failure and do not loosen tests.
  2. Once the suite issue is understood, the supervisor decides whether and when to enqueue PR 457 again.
  3. After a clean queue result, the supervisor merges PR 457.
  4. Re-probe the repository for the next free coordinate immediately before publishing, then publish under supervisor authority and verify the coordinate resolves from a fresh dependency lookup.

Reusable operational knowledge

The queue branch can have a successful GitHub Actions result and still be evicted by its separate kotlin.build result. Inspect the queue commit's buildtest results directly before calling a queue failure a repeat of an earlier test.