Skip to content

Scheduled full test failed: 0e475ceb | 定时全量测试失败: 0e475ceb #7108

Closed

Description

@github-actions

自动跟踪:定时全量矩阵在 0e475ce 上挂了(红灯每个定时 tick 会重试,直到转绿或被新提交取代)。

失败的腿:

此 issue 会在下一次定时全量转绿时自动关闭。

Activity

  1. changed the title [-]定时全量测试失败: 0e475ceb[/-] [+]Scheduled full test failed: 0e475ceb | 定时全量测试失败: 0e475ceb[/+] on Nov 18, 2026
  2. ranxianglei commented on Nov 18, 2026

    @ranxianglei
    Owner

    🤖 Powered by ework · qwen3.8-27b

    (ai: vllm-qwen/qwen3.8-27b)

    Root cause identified for the windows-22-5 / windows-24-5 reds: tests/server-process-listeners.test.ts (the #7026 graceful-shutdown / signal-handler test) — file-level exitCode 1, reproduces in isolation, full retry also fails. CI's own diagnostic: "deterministic break, not a flake".

    • [PR] fix: release process handlers when an embedded server closes #7026 (894835ac94) merged to master today at 01:46 UTC. Its test's 4th case ("graceful shutdown keeps signal handlers until the process exits") sends real SIGINT then SIGTERM to the process and stubs process.exit; on Windows these signals are emulated, so the file exits non-zero deterministically.
    • Confirmed NOT PR-specific: the identical failure signature appears in unrelated PR runs #44245921438, #44246105190, #44249183921 (all windows-latest, 22, 5).
    • ci-fixes has no fix for it yet (and is already an ancestor of the affected PR heads, so merging it is a no-op).

    Suggested fix direction: make the #7026 test Windows-compatible (guard the real-signal cases to non-Windows, or assert the Windows-emulated behavior); if the shutdown code genuinely drops handlers on Windows, fix that instead. Belongs on master/ci-fixes, not individual PR branches.

  3. ranxianglei commented on Nov 18, 2026

    @ranxianglei
    Owner

    (已收)本单已归入根因聚合 issue(token 见聚合单 body),机器人已停止在本单上的工作,修复走聚合 issue 统一出 PR;本单保留不关,修复验证后统一关闭。(聚合单:[Root Cause] c-i-scheduled-full-test-red (2 items),GitHub #7157)

  4. github-actions commented on Nov 18, 2026

    @github-actions
    ContributorAuthor
  5. added a commit that references this issue on Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions