Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

ci-fix: CI failing — Windows PowerShell browser-launch test intermittently hangs past 15s

Aperta
  • Qualcosa non va?
#839 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
powershell, typescript
Ambito
ci-cd, testing-qa

Direzione di ricerca

Start with lib/src/host/browser-launch-env.test.ts, especially the “runs native PowerShell startup code and exits” test, then read browser-launch-env.ts and dor-lib-common/src/spawn.ts. Reproduce the failure on Windows and capture the timed-out child’s stderr to identify where PowerShell stalls. Done means determining whether this is a real hang and fixing it, or documenting the runner-artifact decision and applying a targeted retry.

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

Descrizione

The Standalone Platform Check (windows-latest) job failed on main in run 36534578215. The failing test is runs native PowerShell startup code and exits. Its powershell.exe child ran into browserLaunchEnv's own 15s timeoutMs (Browser launch shell failed (…powershell.exe) … [ETIMEDOUT]).

#834 raised this block's vitest timeout to 20s, reading the earlier 5s failure as a slow cold start. This run shows that reading doesn't hold. The test's timings are bimodal. When it passes, it takes 0.75–2s (main runs 36498700094, 36500139090, 36522172034, 36527315672). When it fails, it is still running at 5s (36500112814 on main, 36515800227 on open-folder) or at 15s (this run). The shell intermittently hangs; it is not merely slow, so another timeout bump would not fix the flake. The trailing EBUSY … rmdir 'dor launch spaces & …' is a side effect: afterEach tries to delete the temp dir while the killed PowerShell still holds it as its cwd.

I haven't found the cause and didn't open a fix. The test runs only on Windows, and the evidence doesn't rule out a real intermittent hang that users with Windows PowerShell as their browser launch shell would also hit. The production budget is the same 15s. Stdin is already 'ignore' in spawnAndCapture, which rules out the usual "powershell waits on an open stdin pipe" hang. A maintainer needs to decide the next step:

  • Investigate on Windows. A run that captures the timed-out child's stderr would show where it stalls; today browserLaunchEnv deliberately drops it.
  • Or treat the hang as a runner artifact and add a vitest retry to this one test, knowing that would also hide a real hang.
Lingua principale
TypeScript
Stelle
5
Fork
1
Merge medio
14h 43m
PR unite (30g)
289

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 diffplug/dormouse

Tutte le issue di diffplug/dormouse

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.