← Priority list

UrlProtocol transport keystone evicted from third queue attempt

Supervisor action is required: PR 457 remains open after queue remote run 8cf670f7 failed 15 of 1261 tests while queue GitHub Actions passed all 1261.

hf-2026-07-31-urlprotocol-transport-keystone-evicted-from-third-queue-attempt

Edit handoff

Add dependency

Complete this handoff

Moves it out of every priority list and into ArchiveArea.

Handoff document

Markdown

Outcome

UrlProtocol pull request https://github.com/CodexCoder21Organization/UrlProtocol/pull/457 was evicted from the merge queue after its third queue attempt. The lane did not re-queue it because the supervisor exclusively owns enqueue and merge actions.

Verified live state

  • Pull request: OPEN, clean, head 4510849637941ae23cee8d41107bc8d8c21cf281
  • Queue commit: 84a8bb54c28f251cfd87b3b94670f33d626e0e5d
  • Queue ref: absent after eviction
  • Queue GitHub build: passed
  • Queue GitHub test run: 1261/1261 passed
    • https://github.com/CodexCoder21Organization/UrlProtocol/actions/runs/30592748085
  • Queue remote run 8cf670f7: 1246/1261 passed, 15 failed

The buildtest unpaged endpoint returns only the first 100 entries. The totals above were verified by fetching all three pages with limit=500.

Exact failures in remote run 8cf670f7

  1. stressTestOrdinaryRelayGossipFanoutDoesNotWaitPerMessageForStalledPeer — stalled gossip callback was not entered.
  2. stressTestPeerRegistryConcurrentAddEvictPreservesObservationInvariant — 30000 ms test timeout.
  3. stressTestRelayLargePayloadLifecycleStartsIndependentHostStopsTogether — concurrent 8 MiB relay call 2 returned an empty value instead of the intact payload.
  4. testConnectionListenerIsolation — slow connection listener was not invoked.
  5. testConnectionRecoveryAfterDisconnect — 30000 ms timeout while reading a libp2p JSON frame.
  6. testGracefulCloseEmitsSingleDisconnectedEvent — 2000 ms loopback dial timeout.
  7. testLargeRequestPayloadTraversesRelay — 30000 ms timeout while quoting the request JSON.
  8. testLibp2pExactPeerRoundTripsHonorCallerResponseBudget — 5000 ms loopback dial timeout.
  9. testNewConnectionsWorkAfterIdleTimeout — 30000 ms timeout.
  10. testOutboundDialAdmissionReleasesPermitAfterSuccessfulDial — 2000 ms loopback dial timeout.
  11. testPeerRegistryAddPeerScalesWithManyServices — 800 peers for 20 rounds exceeded 8 seconds during round 15 at 8006 ms.
  12. testPeerRegistryEvictionPrefersScoreEvidenceOverColdIdentityHeuristic — 30000 ms timeout in bootstrap ranking.
  13. testPeerRegistryIncrementalDuplicateIpv4VictimMatchesPriorRule — 30000 ms timeout in diversity-distance calculation.
  14. testRegisteredRpcHandlerReplacesPreinstalledBinding — 2000 ms loopback dial timeout.
  15. testThousandPeerOstracismScoresFollowBoundedRecords — 30000 ms timeout in PeerScorer.computeSpamFactor.

Comparison with the two prior evictions

  • First prior remote run 44b64191: 1260 passed / 1 failed. The sole failure was testPeerRegistryPartiallyIndexedPopulationUsesExactEvictionFallback, which timed out after 30000 ms.
  • Second prior remote run a648221e: 1250 passed / 11 failed.
  • Eight failures repeat between the second prior run and the current run:
    • stressTestRelayLargePayloadLifecycleStartsIndependentHostStopsTogether
    • testConnectionRecoveryAfterDisconnect
    • testLargeRequestPayloadTraversesRelay
    • testNewConnectionsWorkAfterIdleTimeout
    • testOutboundDialAdmissionReleasesPermitAfterSuccessfulDial
    • testPeerRegistryEvictionPrefersScoreEvidenceOverColdIdentityHeuristic
    • testRegisteredRpcHandlerReplacesPreinstalledBinding
    • testThousandPeerOstracismScoresFollowBoundedRecords

All three queue-branch GitHub Actions test suites passed 1261/1261. The remote failures span callback delivery, loopback dialing, payload delivery, registry work, and per-test deadlines. No evidence-based rerun was performed, and no test limit, payload, iteration, heap, or timeout was changed.

Required next action

The supervisor must decide whether and when to enqueue the pull request again. If it merges, publish the next verified-free UrlProtocol coordinate and confirm that the artifact resolves before allowing the dependent UrlResolver updates.