Windows e2e: stdout has one more gap line than the expected count (fixed seed 4/10, noTypescript)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start from the failing Windows job log for fixed seed 20261105: a declaration fault: noTypescript and compare the 169 oracle-gaps: stdout lines against the expected 168 gaps to isolate the extra line. Then trace where that checkpoint emits gap lines in the e2e harness, using the earlier #73 Windows stdout-count fix as the closest precedent. Done means the fixed-seed Windows run reports exactly 168 lines and the source of the extra line is explained.

Written by the indexing model from the issue text.

Description

windows

Job: https://github.com/TanStack/oracles/actions/runs/43661845394/job/132652674703 (Windows gap report end-to-end oracle, fixed seed 4/10, on #73 at 104376d)

Test: fixed seed 20261105: a declaration fault: noTypescript (9.0 min on windows-latest)

Error:

oracle-gaps.report violated at checkpoint "stdout" (law: greppable stream).
Difference: the stdout has 169 gap lines for 168 gaps: ["oracle-gaps: gap not-distinguished L4 sut.ts:M1 ` process.env.NODE_ENV !== 'production' ` → ` undefined `", "oracle-gaps: gap not-observed L4 sut.ts:M2 ` !== ` → ` === `", "oracle-gaps: gap unreached L6 sut.ts:M3 ` false ` → ` undefined `", ...]

What this is: the stdout of the run has one more gap line than the expected count of gaps, on win32. It is the same family as the earlier Windows stdout-count breach (fixed on #73 for authored mutants). The extra line has not been identified; the full list of 169 lines is in the failing run's log.

Not: the oracle's expected count for this history. Linux runs pass.

Found while reviewing #73 (its body links this issue). Non-blocking: Windows end-to-end is non-blocking under C entry (c) until #79.

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.