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

Windows build times in the CI are highly variable

Aberta
  • Algo errado?
#4,537 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

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
github-actions, node.js
Domínio
ci-cd

Direção de pesquisa

Start with the Windows build time trends linked in the issue and compare the compile jobs that finish in about 20 minutes with those taking over two hours. The issue also points to the Windows JavaScript suite console log and a test-sqlite-session failure; inspect that failure and compare other intermittent failures for the reported out-of-memory condition. Done means identifying likely causes and actionable improvements to build time or test flakiness; the issue names no repository files or tests to change.

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

Descrição

As part of the analysis I was doing for coming up with some CI improvement ideas for https://github.com/nodejs/build/issues/4529 I noted that the Windows builds were extremely variable in terms of build times. While the Linux build tend to run in about 5-30 minutes (it's typically dwarfed by the test time which is now running at close to half an hour) the Windows builds are taking between 20 minutes (best case) but most days there are a few that seem to take over 2 hours for just the compile phase. win-vs2022_clang / win-vs2022_clang-arm64

Creating this issue so we can investigate whether there is any scope for improvement of the build times since (albeit subjectively) I've seen more occurrences of queued windows jobs in the CI recently than other platforms, and the spikiness of the compile jobs could potentially explain why.

I'll also note that here (because it's windows, although it's a different problem) there seems to be a relatively high proportion of failures occurring in the Windows js test suites that should perhaps also be looked at to see if any improvement to flakiness can be done. As an example https://ci.nodejs.org/job/node-test-binary-windows-js-suites/RUN_SUBSET=1,nodes=win10-COMPILED_BY-vs2022_clang/44048/console had one failure in test-sqlite-session. As noted in the CI improvement ideas issue we already have re-run testing but in this case (a 1/10 failure) the job is still marked as a fail so we possibly need to look at utilising this data as each failure in the js-suites one would likely have resulted in a PR test re-run.

08:46:45  failed 1 out of 10
08:46:45 not ok 1056 parallel/test-sqlite-session

That failure was a 08:46:45 # Fatal JavaScript out of memory: GC during deserialization condition - it would be useful to know how many of the other intermittent failures are similar problems.

Linguagem predominante
Jinja
Estrelas
544
Forks
184
Merge médio
4d 16h
PRs com merge (30d)
12

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 nodejs/build

Todas as issues de nodejs/build

Issues semelhantes

Mais issues de DevOps

Receba novas issues na sua caixa de entrada

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