flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)

Aperta
#550 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
56/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bun, github-actions, rust, typescript
Ambito
ci-cd, testing

Direzione di ricerca

Start by reading the four named tests: scripts/check-dco.test.ts, scripts/i18n/runner.test.ts, scripts/i18n/translate.test.ts, and scripts/check-changed.test.ts. Check how bun run release:test sets test timeouts on Windows and how the cargo metadata test handles its cache. Confirm the intermittent timeout locally or in CI; done means the Windows scripts job passes reliably without masking genuine test failures.

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

Descrizione

area: ci os: windows type: bug

Repo scripts (windows-latest) fails intermittently on bun run release:test because tests hit bun's default 5 s timeout (and one its 60 s timeout) on the Windows runner. Everything else in the run passed; a rerun of the failed job passed.

Evidence

Run 44112407920 (PR #462, head 5a0796e0), job 134145061890, test summary:

  • scripts/check-dco.test.ts: a signed-off commit by a real identity passes timed out after 5000 ms.
  • scripts/i18n/runner.test.ts: bun scripts/i18n/check.ts > info findings are hidden unless --info, and never fail the run timed out after 5000 ms.
  • scripts/i18n/translate.test.ts: the prompt > includes at most 20 existing pairs of the same area, never the keys being translated timed out after 5000 ms.
  • scripts/check-changed.test.ts:129: --json --stdin (the atlas_affected plugin) > a crate under crates/ resolves through cargo metadata to its dependents timed out after 60000 ms.

Frequency: 1 occurrence in the 4 or so Windows scripts jobs I watched on 2026-11-17 (the runners were heavily queued). All four tests spawn a child process (git, bun, cargo metadata), which is slow on Windows when the machine is busy.

Suspected cause (not verified)

Spawning git/bun/cargo metadata per test on a contended Windows runner exceeds the default test timeouts. The cargo metadata test has no warm cache on that job. Raising the per-test timeout on Windows (or a CI-wide --timeout), or caching cargo metadata, would be the options.

No fix in the PR where it was seen.

Lingua principale
Rust
Stelle
3
Fork
1
Merge medio
9h 51m
PR unite (30g)
310

Preparare l'ambiente

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 codeatlasdev/atlas

Tutte le issue di codeatlasdev/atlas

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.