mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-10-21 05:40:14 +00:00
* test(managed-agent): add the FG11c Harness-crash fault gates (#14446) * test(managed-agent): harden the FG11c crash gates * docs(managed-agent): recompose the FG11c budget after the FG12b merge * test(managed-agent): hold the scanner while the FG11c crash cases arm The manual run in `turn-crash` and `settled-crash` races a minute boundary: a scheduled occurrence admitted during setup fires the same Session and leaves a second chain of `fireRun` commands, so the exact `:1`, `:2` assertion fails for a reason the case does not gate. Park the scanner for the setup, and release it once the crash is in place so the next minute slot still drives the reconcile. `settled-crash` also arms the revision-3 hold after its POST, but the Harness kicks the wake pump before answering `fire_run`, so the settle can reach the store first and the case then waits for a hold that never fires. Derive the run id, arm the hold, and POST after it. * docs(managed-agent): retarget the FG11c c3 witness to the method Running c3 as written — the open path skips `reconcileRuns` — left `settled-crash` green in 39.6 s with the mutation proven to reach the chunk loaded from `dist/cli.js`: the crashed Harness is re-driven by the next slot's `reconcile_run`, and that route reaches `reconcileRuns()` too, so the single-site mutation is covered by the other caller. Short-circuiting `HostedAutomationSession.reconcileRuns()` turns the case red as the table claims: `expected "completed"` times out at the case's terminal assertion after 216.5 s. Retarget the witness and correct the finding that named the open path as revision 3's only committer. * docs(managed-agent): restate the FG11c budget on the FG12f baseline * docs(managed-agent): record the runtime-broker checkstyle attribution * docs(managed-agent): name the surviving reconcile path behind the c3 green * docs(managed-agent): restate the FG11c budget on the FG13a baseline --------- Co-authored-by: 易良 <1204183885@qq.com> |
||
|---|---|---|
| .. | ||
| archive/managed-agent-schema | ||
| assets | ||
| design | ||
| developers | ||
| e2e-tests | ||
| images | ||
| plans | ||
| superpowers | ||
| users | ||
| verification | ||
| _meta.ts | ||
| evaluation.md | ||
| evaluation.zh-CN.md | ||
| index.md | ||