Skip to content

CI: windows-latest node22 测试分片偶发误红(lineage-reconcile-boot fetch failed、web-routing 事件循环耗尽取消 6 项),rerun 转绿 #3237

Closed

Description

@ranxianglei

来源: #3227 (#3227) 分析 Codex Responses proxy developer-item hoist 修复时发现

查重: 与 #3228(wire-exit 墙钟断言,已有 PR #3233)、#3220(event-loop 卡顿击穿毫秒时钟断言,已关)同属「CI 分片误红需人工 rerun」症状家族,但失败签名不同(不同文件/测试/错误行)且机制未确认 —— 按失败签名分立跟踪;若后续诊断出与既有条目同一根因,再归并。

失败签名(PR #3232,commit 2d75670,run 38676555500;均为 windows-latest + node 22 分片)

A. tests/lineage-reconcile-boot.test.ts AC10(job test (windows-latest, 22, 1))

not ok 1379 - AC10: reconcile is idempotent across repeated boots
error: 'fetch failed'  (TypeError, undici)
stack: async chat (tests/lineage-reconcile-boot.test.ts:126) → setupForkOnDisk (:211)

对本地 mock upstream 的连接级失败,不是断言失败。同 run 其余 7 个矩阵 cell(ubuntu/windows × 22/24 × 3 shards)全绿;该文件无任何 codex/user-agent 引用,与 #3227 的 diff 无关(diff 条件对无 UA 请求退化为旧行为)。

B. tests/web-routing.test.ts 事件循环耗尽(job test (windows-latest, 22, 3))

  • 6 个子测试(PUT /__bili/config 家族,TAP fix: seam forensics re-notes outbound body on proxy-initiated re-send hops (#1894) #1899–1904)failureType: 'cancelledByParent',伴随 Promise resolution is still pending but the event loop has already resolved
  • TAP 汇总 fail 0 / cancelled 6,exit 1:某个 Promise 永不 settle,事件循环排空后 node --test 取消了父文件下其余待决子测试
  • 该文件同样无 codex/user-agent 引用

处置记录

  • 已对 run 38676555500 发起 rerun-failed-jobs(HTTP 201),两个分片 rerun 后 26/26 全绿 → 判定为 runner 瞬态(flake),非 PR 回归
  • 各单次出现、机制未确认。复现路径未知前无定向修法;后续任一签名再出现(master 或其他 PR)时把证据补进本 issue 对应小节,并按「同一症状一个 issue」政策在本 issue 内以子缺陷清单管理,不再另立

建议排查方向(供后续参考,非结论)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions