random seed: an edit sequence through the daemon: authored mutant a2 runs to its backstop (timeout, owed killed), seed 964713679 on #99

Aperta
#167 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, vite
Ambito
testing-qa

Direzione di ricerca

Start with the e2e oracle command and seed in the counterexample, then inspect the authored mutants law at the cli checkpoint and the history details in the issue. The report identifies a timeout in file b's authored:a2 copy, but the cause is still unknown and history replay depends on #157. Done means reproducing and explaining the timeout; the issue assigns this investigation to #99's author for a later follow-up round.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Counterexample

A random seed of the e2e oracle on #99 at 83a0b3a8 (pool, then twice more, and on macOS: reproducible):

ORACLE_SEED=964713679 ORACLE_PATH=0 ORACLE_PROPERTY='oracle-gaps.report' ORACLE_UNIT='random seed: an edit sequence through the daemon' GAP_E2E_SHRINKS=0 vitest run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t '^oracle-gaps\.report(?: | > )random seed: an edit sequence through the daemon$'
  • Law authored mutants, at checkpoint cli (the cold run): the authored mutant a2 is timeout, owed killed. Its result is {"outcome":"timeout","cause":"backstop"}.
  • File b's copy for authored:a2 runs to its backstop: 20.05 s, where the limit is 20 s plus 3 s × 0.018 s. Its file's unmutated run takes 0.018 s.
  • The history (cut at 2,000 characters in the log) has:
    • two functions, if x > 4 push and push, owned by a and b;
    • a test of file a with input 5, and a test of file b with input 1 on f1;
    • authored: {stmt: 0, kind: apply}, secondAuthored: true, ordinary: true, contexts: 4, budget: one;
    • cliPath: spaced, unbuiltDep: true, packageType: commonjs, configFile: vite.config.cts, concurrentStart: true.
  • The same seed passes on main 97a4e7a, but there it draws a different history, because #99 shifts the draws. So base attribution needs a replay by history (#157), which is not built yet.

What is known

  • The copy is not idle by state. If it were, it would be killed by no progress. It also has no call budget (an authored copy counts no calls).
  • The copy either loops synchronously, or waits before any test starts. Before a test starts the sampler does not judge idle; an example is a module fetch over the runner's RPC (#148).
  • It is not caused by #99's clocked-by-state hook: with that hook's completion record disabled, the unit fails the same way.

Owner

#99's author, in the next round on the deterministic-cuts follow-ups. Replay the full history on main once #157 lands; if main fails it too, this does not block #99 (M, "Main's determinism failures").

Lingua principale
JavaScript
Stelle
5
Fork
1
Merge medio
11h 18m
PR unite (30g)
66

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TanStack/oracles

Tutte le issue di TanStack/oracles

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.