Windows e2e: w_fastturn's work-bound kill is not-observed on win32 (sut.ts:M91, every outcome class)

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

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

研究方向

Start with classify.mjs at judgeMutant and rose, then compare the win32 and macOS traces for sut.ts:M91 to find which work-bound condition differs. Check the test's work agreement, route, clocked status, and call count on each platform; the cause is not yet known. Done means the same mutant is classified as killed on win32 and macOS under the fixed-seed end-to-end test.

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

描述

windows

Summary

On win32, the witness mutant src/sut.ts#w_fastturn:if-false:if ( x > 2 ) { out . push ( 's' + x ) ; return ; } (sut.ts:M91, line 113) is reported as the gap not-observed. On Linux and macOS the same mutant is killed by its work bound. The oracle's model owes killed. This is a cross-platform classification difference. It is not a stream defect.

Under the old greppable-stream comparison (a count of stdout gap lines against the model's gaps), this difference showed as "the stdout has 122 gap lines for 121 gaps". With the stream law compared against results.json by id (the PR that fixes the gap-line count), the same run fails under classification and names this site.

Traces

  • win32: main at 4d3c8a9, run 43693786590, job 132749781500 (Windows gap report end-to-end oracle (fixed seed, 2/10)), unit fixed seed 20261105: every outcome class. stdout and stderr list the same 122 gap lines, with no duplicates. The extra line is oracle-gaps: gap not-observed L113 sut.ts:M91 + "x > 2 → false" + `.
  • macOS, same unit at 4d3c8a9, local: results.json holds {"id":"sut.ts:M91","outcome":"killed","by":["t36 > fixed seed 37"],"laws":["work bound"]}, and the run lists 121 gaps, the owed number.

What is not known

The cause on win32 is not identified. A kill by work bound needs four things: the two unmutated runs agree on the test's work, the route is reproducible or random, the row is not clocked, and the call count rises past the bound (classify.mjs judgeMutant, rose). One of these differs on win32. A clocked row is one candidate, since w_fastturn's tests wait a turn. This is not confirmed.

Authority

P4 (register): a counterexample is filed with its trace. "Determinism under load" applies: an outcome must not depend on the platform's timing. P3: a declared work bound is a law.

主要語言
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 摘要。