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

`rhel8-x64` executors in the CI frequently to have an unexpected 25 minute "pause" around the doc gen execution pase

Aperta
  • Qualcosa non va?
#66,878 0 commenti 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
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js
Ambito
ci-cd, devops

Direzione di ricerca

Start with the three linked CI logs and compare the time between the out/doc/api setup and npm finishing on the RHEL8 x64 workers. The issue points to doc generation and npm as possible areas, but does not identify a cause; determine where the pause occurs and whether it is specific to those workers. Done means explaining the source of the delay and identifying a way to resolve it.

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

Descrizione

Spotted today while looking at the jobs which were taking longest and determining that the rhel8-x64 ones are regularly taking over an hour in total. it doesn't seem to affect RHEL8 on ppc64le or other x64 platforms from an initial look which take no more than around 2 minutes for the same section. The rhel8-x64 builds seem to pause and produce no build output on those machines. It's unclear why but it may be while running npm. Possible resource starvation, I/O on disk or network or something else but perhaps @nodejs/doc-kit might be able to provide some insight as to whether this is likely to be in the doc generation and if so be able to provider some insight on how we might be able to resolve it. These log snippets are from three machines across two providers:

Job 73039 on test-ibm-rhel8-x64-2:

14:09:09 Building addon in /home/iojs/build/workspace/node/test/sqlite/test_sqlite_extensions
14:09:09 mkdir -p out/doc
14:09:09 cp doc/node-config-schema.json out/doc
14:09:09 mkdir -p out/doc/api
14:34:58 cp -r doc/api out/doc
14:34:58 npm warn cli npm v12.1.0 does not support Node.js v27.0.0-pre. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
14:34:58
14:34:58 added 297 packages, and audited 298 packages in 9s
14:34:58
14:34:58 148 packages are looking for funding
14:34:58   run `npm fund` for details
14:34:58
14:34:58 found 0 vulnerabilities

Job 74040 on test-ibm-rhel8-x64-1:

14:08:39 Building addon in /home/iojs/build/workspace/node/test/sqlite/test_sqlite_extensions
14:08:48 mkdir -p out/doc
14:08:48 cp doc/node-config-schema.json out/doc
14:08:48 mkdir -p out/doc/api
14:08:48 cp -r doc/api out/doc
14:08:48 npm warn cli npm v12.1.0 does not support Node.js v27.0.0-pre. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
14:08:48
14:08:48 added 297 packages, and audited 298 packages in 9s
14:34:31
14:34:31 148 packages are looking for funding
14:34:31   run `npm fund` for details
14:34:31
14:34:31 found 0 vulnerabilities
14:34:31 Clean up any leftover processes, error if found.

Job 74037 on test-digitialocean-rhel8-x64-1:

13:20:23 Building addon in /home/iojs/build/workspace/node/test/sqlite/test_sqlite_extensions
13:20:23 mkdir -p out/doc
13:20:23 cp doc/node-config-schema.json out/doc
13:20:23 mkdir -p out/doc/api
13:20:23 cp -r doc/api out/doc
13:20:23 npm warn cli npm v12.1.0 does not support Node.js v27.0.0-pre. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
13:49:43 
13:49:43 added 297 packages, and audited 298 packages in 10s
13:49:43 
13:49:43 148 packages are looking for funding
13:49:43   run `npm fund` for details
13:49:43 
13:49:43 found 0 vulnerabilities
Lingua principale
JavaScript
Stelle
123k
Fork
39.9k
Merge medio
4g 13h
PR unite (30g)
235

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/node

Tutte le issue di nodejs/node

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.