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

Offen
#550 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
56/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
bun, github-actions, rust, typescript
Bereich
ci-cd, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
3
Forks
1
Ø Merge
9 Std. 51 Min.
Gemergte PRs (30 T.)
310

Entwicklungsumgebung

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

Alle Issues in codeatlasdev/atlas

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

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