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

Offen
#114 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
testing-qa

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
JavaScript
Sterne
5
Forks
1
Ø Merge
8 Std. 31 Min.
Gemergte PRs (30 T.)
60

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TanStack/oracles

Alle Issues in TanStack/oracles

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.