Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
#66,878 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
1-2 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
javascript, node.js
Domaine
ci-cd, devops

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
JavaScript
Étoiles
123k
Forks
39.9k
Merge moyen
4 j 14 h
PR mergées (30 j)
235

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/node

Toutes les issues de nodejs/node

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.