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

Aberta
#550 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
56/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
bun, github-actions, rust, typescript
Domínio
ci-cd, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
3
Forks
1
Merge médio
9h 51min
PRs com merge (30d)
310

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codeatlasdev/atlas

Todas as issues de codeatlasdev/atlas

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.