You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An isolated neighboring-test run during #2616 AC2b verification exposed eight failures in packages/agents/src/core/subagentNonInteractive.issue3535.test.ts. The same eight failures reproduce against archived sources from base commit cdcbb07fe, before the load-balancer admission move in 2e4256cd4.
Reproduce from packages/agents:
bun test --timeout 30000 ./src/core/subagentNonInteractive.issue3535.test.ts
Observed: 9 pass, 8 fail. Each failure throws TypeError: this.messageBus.subscribe is not a function at packages/agents/src/scheduler/confirmation-coordinator.ts:193, reached through CoreToolScheduler construction and packages/agents/src/session/assembleSchedulerOwner.ts:19,31.
Expected: the fixture supplies the required message-bus subscription operation, and the existing fatal-error/recovery assertions execute and pass. Keep the assertions and scheduler subscription requirements unchanged.
Evidence in the assigned tmp/w2616b worktree: tmp/verify2616-b/ac2b/r4-test-425.log, r4-3535-retry.log, and r4-3535-base.log. The latter uses archived agents, providers, other package sources and scripts from cdcbb07fe, with existing installed dependencies. No source or test changes were made for this defect.
Already fixed on the issue2616-final branch by 717d064, which hasn't reached the lane branch this report came from.
The fixture was the only cause. 2386c08 added two retry arguments ahead of messageBus in the private SubAgentScope constructor. This test called that constructor positionally through an unknown[] cast with the old argument order, so OUTPUT_CONFIG ended up in the message-bus slot. Production builds scopes through SubAgentScope.create and the orchestrator, and both pass the arguments in the right order.
717d064 changes only the test so that it uses SubAgentScope.create with the typed scopeInputs helper. The file now passes 17/17. That commit is on the pushed issue2616-final head.
Activity
github-actions commentedon Oct 12, 2026
LLxprt Issue Planner — infrastructure failure
The autonomous planner failed with exit code 1. Please inspect the workflow logs (Run planner agent section) and re-run once resolved.
acoliver commentedon Oct 12, 2026
Already fixed on the
issue2616-finalbranch by 717d064, which hasn't reached the lane branch this report came from.The fixture was the only cause. 2386c08 added two retry arguments ahead of
messageBusin the privateSubAgentScopeconstructor. This test called that constructor positionally through anunknown[]cast with the old argument order, soOUTPUT_CONFIGended up in the message-bus slot. Production builds scopes throughSubAgentScope.createand the orchestrator, and both pass the arguments in the right order.717d064 changes only the test so that it uses
SubAgentScope.createwith the typedscopeInputshelper. The file now passes 17/17. That commit is on the pushedissue2616-finalhead.