flaky: atlas-host pty::tests::a_title_* fail on loaded Linux CI runners

オープン
#549 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
72/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
rust
領域
cli, testing

調査の方向性

Start with crates/atlas-host/src/pty/tests.rs, especially the two failing title tests around lines 545 and 569, and inspect how they wait for the shell to exit and collect pty_title events. Run these tests repeatedly under load to reproduce the timing failure. Done when the tests reliably observe the expected title events with a deadline and pass in the Linux CI run.

索引モデルが issue の本文から書いたものです。

説明

area: terminal os: linux type: bug

atlas-host pty::tests::a_title_* fail intermittently on the Linux CI runner (Rust (Linux)), unrelated to the PR under test. A rerun of the failed job passes.

Evidence

  • Run 44101988098 (PR #461, head eb47a231), job 134104287831: FAIL atlas-host pty::tests::a_title_that_returns_to_an_earlier_value_is_a_change, at crates/atlas-host/src/pty/tests.rs:569:
    assertion left == right failed left: ["x"] right: ["x", "y", "x"]. The rerun of the same head passed.
  • Run 44104330309 (PR #487, head 2d01391f), job 134114260709 (Linux): FAIL atlas-host pty::tests::a_title_repeated_by_the_program_is_pushed_once at tests.rs:545. The rerun passed.
  • Frequency: 2 failures in the roughly 8 Rust (Linux) attempts I watched on 2026-11-17, while the runners were heavily queued (many PRs at once). Both ran in the full nextest run (4171 tests, 4 threads), not alone.

Suspected cause (not verified)

Both tests drive a shell that prints OSC titles 20 ms apart (sleep 0.02) and rely on each landing in its own 8 ms coalescing window of the pty reader, then call until_exited and read pty_title events with try_recv. On a loaded runner a 20 ms sleep can stretch, or the reader can drain two OSCs in one window, or the exit can be observed before the last pushes are flushed; the failure shows only the first title arriving (["x"]). The tests wait for the process to exit, not for the expected number of titles. Waiting for the expected events (with a deadline) instead of a fixed sleep and a post-exit drain would remove the timing dependency.

No fix in the PRs where it was seen.

主要言語
Rust
スター
3
フォーク
1
平均マージ
9時間 51分
マージ済み PR(30日)
310

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

codeatlasdev/atlas のほかの issue

codeatlasdev/atlas の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。