gap CLI: a run under load can end non-zero (an internal error) where it should complete

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

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

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

評価

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

調査の方向性

Start from packages/oracles and run the failing shard command with the replay env vars (ORACLE_SEED=20261105 ORACLE_PATH=1 ORACLE_PROPERTY=oracle-gaps.report) while a CPU hog saturates the machine, as the issue's Next section proposes. Read oracle-gaps/vitest.config.mjs and scripts/pr-shards.mjs to understand shard selection, and note that #55 now prints the error log on exit 3. Done means the shard-3 e2e run completes exit 0 under load, with the brokenOwner history blocked rather than refused.

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

説明

Summary

Under load, the gap CLI sometimes ends a run with a non-zero exit where the run should complete. Twice it was an internal error ("This is a bug in oracle-gaps"). The e2e oracle's fixed-seed shard 3 failed in 2 of 8 Linux runs on #55's head. Each failure had a different symptom, and neither one reproduces when the unit runs alone.

Traces

  1. CI, job 132489470739 (run 43608937018), commit 16f510c, "Gap report end-to-end oracle (fixed seed, 3/3)":
    • Unit: fixed seed 20261105: generated, history ORACLE_PATH=1 (fault brokenOwner).
    • Error: a history entered "refused brokenOwner", which the property does not declare.
    • Meaning: the CLI exited non-zero on a brokenOwner history. The history owes exit 0 with blocked mutants (blocked by brokenOwner). The log does not show which non-zero exit or its error.log.
    • Replay: ORACLE_SEED=20261105 ORACLE_PATH=1 ORACLE_PROPERTY='oracle-gaps.report' ORACLE_UNIT='random seed: generated' vitest run -t '^oracle-gaps\.report(?: | > )random seed: generated$'
  2. Classic Arca VM, tag r55-gen-shard3, commit edb24ba (16f510c plus a test-only diagnostic), the same shard-3 command:
    • Unit: fixed seed 20261105: an edit sequence through the daemon, step dieMidCheck.
    • Error: through the daemon at dieMidCheck: the run wrote a line on stderr that is not a line of the stream: This is a bug in oracle-gaps, not in your oracle. Its stack is in <package>/out-daemon/error.log.
    • The VM was shared with another session's long loops when this ran.

The shard command, from packages/oracles:

pnpm exec vitest --run --maxWorkers=2 --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "$(node scripts/pr-shards.mjs pattern oracle-gaps-fixed-seed 3)"

Tally

Commit Where Shard-3 runs Failed
16f510c (#55 head) CI, Classic Arca, Arclets 8 2
35422e3 (main) Classic Arca, Arclets 6 0
ed091f3 (#55 before the #58 merge) Arclets 4 0

The unit generated alone passed on 16f510c locally (macOS) and on the VM, and on main locally. All 12 runs on the dedicated Arclets passed, with no internal error.

Next

  • Reproduce under load on purpose: shard 3 with a CPU hog on the Arclets, 4 runs on #55's head (with the diagnostics, which print each exit-3 run's error.log) and 4 on main. The result decides whether this is #55's or older.
  • #55 (b959d4c) now makes the incremental violation print a cold run's error log when that run exits 3, so the next failure in CI shows its stack.
  • Related: the deterministic-cut follow-up (cut runs by work count, not wall time; "determinism under load"), which targets timing-dependent outcomes.

This issue was written by Isaac.

主要言語
JavaScript
スター
5
フォーク
1
平均マージ
8時間 31分
マージ済み PR(30日)
60

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

TanStack/oracles のほかの issue

TanStack/oracles の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

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

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