gap CLI: a run under load can end non-zero (an internal error) where it should complete

Ouverte
#83 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
30/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
javascript, nodejs
Domaine
cli, testing

Piste de recherche

Start from packages/oracles and run the failing shard command with the replay env vars (ORACLE_SEED=20261105 ORACLE_PATH=1 ORACLE_PROPERTY=oracle-gaps.report) while a CPU hog saturates the machine, as the issue's Next section proposes. Read oracle-gaps/vitest.config.mjs and scripts/pr-shards.mjs to understand shard selection, and note that #55 now prints the error log on exit 3. Done means the shard-3 e2e run completes exit 0 under load, with the brokenOwner history blocked rather than refused.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Summary

Under load, the gap CLI sometimes ends a run with a non-zero exit where the run should complete. Twice it was an internal error ("This is a bug in oracle-gaps"). The e2e oracle's fixed-seed shard 3 failed in 2 of 8 Linux runs on #55's head. Each failure had a different symptom, and neither one reproduces when the unit runs alone.

Traces

  1. CI, job 132489470739 (run 43608937018), commit 16f510c, "Gap report end-to-end oracle (fixed seed, 3/3)":
    • Unit: fixed seed 20261105: generated, history ORACLE_PATH=1 (fault brokenOwner).
    • Error: a history entered "refused brokenOwner", which the property does not declare.
    • Meaning: the CLI exited non-zero on a brokenOwner history. The history owes exit 0 with blocked mutants (blocked by brokenOwner). The log does not show which non-zero exit or its error.log.
    • Replay: ORACLE_SEED=20261105 ORACLE_PATH=1 ORACLE_PROPERTY='oracle-gaps.report' ORACLE_UNIT='random seed: generated' vitest run -t '^oracle-gaps\.report(?: | > )random seed: generated$'
  2. Classic Arca VM, tag r55-gen-shard3, commit edb24ba (16f510c plus a test-only diagnostic), the same shard-3 command:
    • Unit: fixed seed 20261105: an edit sequence through the daemon, step dieMidCheck.
    • Error: through the daemon at dieMidCheck: the run wrote a line on stderr that is not a line of the stream: This is a bug in oracle-gaps, not in your oracle. Its stack is in <package>/out-daemon/error.log.
    • The VM was shared with another session's long loops when this ran.

The shard command, from packages/oracles:

pnpm exec vitest --run --maxWorkers=2 --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "$(node scripts/pr-shards.mjs pattern oracle-gaps-fixed-seed 3)"

Tally

Commit Where Shard-3 runs Failed
16f510c (#55 head) CI, Classic Arca, Arclets 8 2
35422e3 (main) Classic Arca, Arclets 6 0
ed091f3 (#55 before the #58 merge) Arclets 4 0

The unit generated alone passed on 16f510c locally (macOS) and on the VM, and on main locally. All 12 runs on the dedicated Arclets passed, with no internal error.

Next

  • Reproduce under load on purpose: shard 3 with a CPU hog on the Arclets, 4 runs on #55's head (with the diagnostics, which print each exit-3 run's error.log) and 4 on main. The result decides whether this is #55's or older.
  • #55 (b959d4c) now makes the incremental violation print a cold run's error log when that run exits 3, so the next failure in CI shows its stack.
  • Related: the deterministic-cut follow-up (cut runs by work count, not wall time; "determinism under load"), which targets timing-dependent outcomes.

This issue was written by Isaac.

Langage dominant
JavaScript
Étoiles
5
Forks
1
Merge moyen
8 h 31 min
PR mergées (30 j)
60

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TanStack/oracles

Toutes les issues de TanStack/oracles

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.