Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#839 9 comentários 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
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
42/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
powershell, typescript
Domínio
ci-cd, testing-qa

Direção de pesquisa

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.

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

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
5
Forks
1
Merge médio
10h 50min
PRs com merge (30d)
494

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

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

Todas as issues de diffplug/dormouse

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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