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
{{ message }}
Repository navigation
Main CI failed: Qwen Code CI — src/serve/hosted-harness-session.test.ts > … > parks an admitted prompt when model request preparation fails (+1 more) #14101
Test (ubuntu-latest, Node 22.x) — failed in step Run tests and generate reports
Failing tests
src/serve/hosted-harness-session.test.ts > Hosted Harness no-tool session > parks an admitted prompt when model request preparation fails
src/serve/hosted-harness-session.test.ts > Hosted Harness no-tool session > retains cleanup debt after interrupted channel settlement until original-owner release succeeds
This issue is labeled for autofix so the existing agent can create a repair PR.
It is deduped by failing test, so every later commit that hits the same
failure is appended below instead of opening another issue.
🤖 The scheduled autofix agent is picking this issue up. It will attempt to establish the current behavior, implement the requested change, run E2E verification, and open a pull request linked to this issue. If the attempt fails, this claim will be withdrawn so a human can take over.
Maintainers: comment or assign someone to stop future automated attempts, or add the autofix/skip label.
I reproduced the cleanup-debt case as an overlap between the wake retry and a passive load. Besides the extra release, a late failed retry can re-block a Session after cleanup succeeds. I fixed both in #15482; the unchanged regressions fail with the old production code and pass with the fix. Full Harness/approval and related recovery checks pass. This addresses the cleanup case here, not the separate prompt-parking report.
Activity
qwen-code-dev-bot commentedon Oct 13, 2026
🤖 The scheduled autofix agent is picking this issue up. It will attempt to establish the current behavior, implement the requested change, run E2E verification, and open a pull request linked to this issue. If the attempt fails, this claim will be withdrawn so a human can take over.
Maintainers: comment or assign someone to stop future automated attempts, or add the
autofix/skiplabel.doudouOUC commentedon Oct 13, 2026
根因分析
CI-TEST-REGRESSION — commit
53579861daba(fix(serve): resume committed file results after runtime retirement #14059) 引入的回归。回归确认
44ddf79ef4e8(run 38418699275, 2026-10-13T15:03Z) 的Test (ubuntu-latest, Node 22.x)job success:✓ src/serve/hosted-harness-session.test.ts (459 tests) 188409ms——全部 459 个测试通过。53579861daba(run 38410683888, job 115369140703) 同一 test file 2 个测试失败(×3 attempts = 6 fails)。53579861daba修改了 3 个源文件 + 重写了hosted-recovery.test.ts:hosted-workspace-tool-turn.ts(+68/-1):新增retiredOwnerResults状态 +confirmReplacedHostedTurnOwner自动恢复逻辑hosted-turn-cleanup.ts(+61/-7):抽取cleanupIdentity+ 新增confirmReplacedHostedTurnOwner函数hosted-file-history.ts(+4/-1):放宽canSettleHostedFileHistory的record参数类型为Pick<…, 'pendingTurn'|'pendingUndo'|'pendingMessageId'>hosted-harness-session.test.ts未被此 commit 修改(parent 与 new byte-identical 25646 行)。失败 1:
parks an admitted prompt when model request preparation fails测试用
LlmRequestPreparationErrormock 模型准备失败,期望 prompt 被 park (hasActivePrompt:false, recoveryBlocked:true),实际 prompt 仍 active 且 recovery 未阻塞。该测试使用
app()(无 broker、无 toolProfile),属Hosted Harness no-tool sessiondescribe 块。新代码在resumeCommittedResults(hosted-workspace-tool-turn.ts:1993-2050) 中新增的HOSTED_WORKSPACE_FILE_PROFILE自动恢复路径不应直接触发(无 file historypendingTurn),但finish()的 guard 从if (!this.acquired) return;改为if (!this.acquired && !this.retiredOwnerResults) return;(:6893),以及acquire()新增retiredOwnerResultsearly-throw(:6898),可能通过共享代码路径影响了 no-tool session 的模型准备失败处理流程。失败 2:
retains cleanup debt after interrupted channel settlement until original-owner release succeeds测试通过
prewriteChannelWriteInterruption(true)预写 channel turn + cleanup debt,然后app(true)恢复加载,期望release被调用 1 次(recoveryBlocked:true)。新代码
confirmReplacedHostedTurnOwner(hosted-turn-cleanup.ts:138-183) 在resumeCommittedResults(:2034) 中被调用,条件为!saved?.pendingTurn && !saved?.pendingUndo(:1994-1995)。但测试 setup 通过commitHostedFileHistory设置了pendingTurn: channelTurn,因此saved.pendingTurn非 null →!saved?.pendingTurn为 false → 新自动恢复路径不应触发。然而
release被调用 0 次(期望 1 次),说明原有的reconcileHostedTurnCleanup调用路径(cleanup():6924-6929)被新代码阻断。可能的机制:新代码在resumeCommittedResults的if (saved?.pendingTurn)分支(:1891)内部行为发生变化——canSettleHostedFileHistory调用的参数类型被放宽后,可能接受了之前会被拒绝的部分对象,改变了恢复流程的分支走向。建议
resumeCommittedResults在saved.pendingTurn存在时的新旧路径差异——特别是canSettleHostedFileHistory参数放宽后是否导致 settle 检查行为变化。finish()guard!this.retiredOwnerResults是否在 no-tool session 路径意外允许了不应继续的 finish。hosted-recovery.test.ts同步重写了对应测试(+251/-111),新增了 9 个参数化 case,但hosted-harness-session.test.ts中的这两个测试未同步更新——可能存在测试期望与新行为不匹配。6212189f中hosted-workspace-tool-turn.ts与53579861dababyte-identical(未修复),CI run 38435473057 仍在排队。test(serve): widen hosted recovery waitFor windows for CI contention (Q…
test(serve): widen the bare-load compensation test's recovery waits
test(serve): widen the hosted cancel waitFor windows for CI contention (
fix(managed-agent): bound retry loops with terminal states (#13219)
fix(managed-agent): tenant-wide InnoDB locks must not wedge unrelated…
test(serve): widen the Hosted Harness idle wait on loaded runners (#1…
jabrailkhalil commentedon Oct 24, 2026
I reproduced the cleanup-debt case as an overlap between the wake retry and a passive load. Besides the extra release, a late failed retry can re-block a Session after cleanup succeeds. I fixed both in #15482; the unchanged regressions fail with the old production code and pass with the fix. Full Harness/approval and related recovery checks pass. This addresses the cleanup case here, not the separate prompt-parking report.