Repository navigation
Commit b8e8a48
easonLiangWorldedtech
chore(ci): request a fresh run for the flaky restart-persistence step
No code change. This empty commit exists only to obtain a new CI run, because the required e2e-mock check is red at c4ca658 and the failed job cannot be re-run with the token available here (POST /repos/Zoo-Code-Org/Zoo-Code/actions/runs/37880099804/rerun-failed-jobs -> 403 Must have admin rights to Repository).
Why the red is not caused by this branch:
- In job 113657575830, step 14 'Run mocked E2E tests' = success; only step 15 'Run mocked restart-persistence E2E test' failed. The create phase passed ('persists completed task across a fresh extension host', 1 passing); the verify phase threw TaskMessagesReadError: Failed to read task messages for 01a11ec0-9f7e-72db-9721-1c8b2d4d28f4 at /tmp/roo from readTaskMessages <- Task.resumeTaskFromHistory <- TaskScheduler.schedule, then 'Error: Timeout after 30s' (out/suite/utils.js:15).
- The previous head on this same branch, cf9206a, passed both steps (run 37516254245, 2026-10-06). The only commit between cf9206a and c4ca658 changes src/core/task/__tests__/Task.spec.ts (+13/-2), a Vitest unit-test file the mocked E2E suite never loads; no production file changed and the branch base is unchanged (7214352).
- The identical signature appears on unrelated branches: run 37762259575 (vps2-f2c), run 37706659841 (feat/chat-input-model-selector, same TaskMessagesReadError), run 37626907243 (feat/dte-v2-3-task-runtime-effort).
- Four sibling PRs carrying the same U1 Task.ts content passed this step: #1929 run 37873787271, #1928 run 37854340884, #1931 run 37833581055, #1932 run 37774292614.
Evidence note on the PR: #1927 (comment)1 parent c4ca658 commit b8e8a48
0 file changed
0 commit comments