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

Windows build times in the CI are highly variable

Aperta
  • Qualcosa non va?
#4,537 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

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

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Jinja
Stelle
544
Fork
184
Merge medio
4g 16h
PR unite (30g)
12

Preparare l'ambiente

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

Tutte le issue di nodejs/build

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.