Skip to content

test(runtime-host): investigate owned candidate connection flake #3190

Closed

Description

@M4n5ter
English

Summary

The Runtime Host test owned Host exits promptly after its first connection closes flakes under the full CI suite.

In CI run 32101082229, test_runtime_host completed 962 of 963 tests and failed at owned-candidate.test.ts:66:

  • expected: connected
  • actual: failed
  • configured election deadline: 2 seconds

PR #3188 does not change Runtime Host code or its test inputs, so this is not attributable to that PR.

Impact

Unrelated pull requests can receive a blocking red CI result without a product regression.

Suggested investigation

Preserve the concrete failure reason in this test before asserting the result kind, then determine whether the two-second election deadline or candidate readiness path is timing-sensitive under full-suite CI load.

AI use

OpenAI Codex assisted with log triage and issue drafting. M4n5ter is the reporter of record.

中文

摘要

Runtime Host 测试 owned Host exits promptly after its first connection closes 在完整 CI 套件中出现不稳定失败。

在 CI run 32101082229 中,test_runtime_host 的 963 项测试通过了 962 项,最终在 owned-candidate.test.ts:66 失败:

  • 预期:connected
  • 实际:failed
  • election deadline:2 秒

PR #3188 没有修改 Runtime Host 代码或测试输入,因此该失败并非由该 PR 引入。

影响

无关 PR 可能在没有产品回归时收到阻塞性的红色 CI。

建议调查方向

在断言 result kind 前保留具体 failure reason,再判断两秒 election deadline 或 candidate readiness 路径是否会在完整 CI 负载下产生时序问题。

AI 使用说明以英文区为准。

Activity

  1. added 7 commits that reference this issue on Aug 18, 2026
    79fa1ce
    f944c30
    95e0072
    386e522
    368409a
    1116963
    8ca108e
  2. M4n5ter commented on Aug 19, 2026

    @M4n5ter
    MemberAuthor

    Reproduced again locally on 2026-08-19 while validating #3238 at commit 6fd199626. Two full Runtime Host suite runs failed with the same owned Host exits promptly after its first connection closes result (expected connected, received failed), while the focused owned-candidate.test.js run passed all 5 tests. #3238 only changes Windows startup diagnostics and this failure is independent of that diff.

  3. added a commit that references this issue on Aug 20, 2026
    803edc1
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions