Self-oracle counterexample: timeout presentation not exercised (seed 569029462)

未關閉
#51 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
22/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript
領域
testing

研究方向

The failure is the self-oracle.framework property, unit random seed: generated, law timeout at checkpoint child, replayed with seed 569029462 and the ORACLE_PATH given in the issue, run through vitest with a -t name filter. Start by reproducing that single replay and reading how the generator builds the timeout step. Done means either the generator stops producing histories whose timeout cannot fire, or the timeout presentation is shown to be exercised, or the trace is recorded in the coverage map.

由索引模型根據 Issue 內容生成。

描述

A random-seed run of the framework self-oracle on main found a counterexample that fails law timeout. This happened after #31 (e2af13a).

  • Run: PR #47's first CI run, "Framework self-oracle (8/8)". #47 changes only how CI splits the tests into jobs. A rerun with a new seed passed.
  • Unit: self-oracle.framework > random seed: generated
  • Violation: checkpoint "child", law timeout.
  • Difference: "timeout presentation was not exercised"
  • Replay:
    ORACLE_SEED=569029462 ORACLE_PATH=1:0:0:0:0:0:0:0:0:0:0:0:0:0:2:1:1:1:1:1:1:1:1:1:1:1:1:4 ORACLE_PROPERTY='self-oracle.framework' ORACLE_UNIT='random seed: generated' vitest run -t '^self-oracle\.framework(?: | > )random seed: generated$'
    

A generated history appears to declare a timeout presentation that its run never reaches. Either the grammar generates a history whose timeout cannot fire, or the timeout path does not present as the model owes. Fix it oracle-first, or record it in the coverage map with this trace.

This issue was written by Isaac.

主要語言
JavaScript
星號
5
分支
1
平均合併
8 小時 31 分鐘
30 天內合併 PR
60

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TanStack/oracles 的其他 Issue

查看 TanStack/oracles 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。