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

Open
#114 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
testing-qa

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
JavaScript
Stars
5
Forks
1
Avg merge
6h
Merged PRs (30d)
56

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TanStack/oracles

All issues in TanStack/oracles

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.