Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#1,174 4 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

@ovflowd arbeitet bereits daran.

Seit 25.10.2026.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
javascript, node.js
Bereich
ci-cd, documentation

Rechercherichtung

Start with the CI log snippets and compare the rhel8-x64 runs around the out/doc copy and npm install output with the same stage on other platforms. The reported pause lasts about 25 minutes across machines, but the issue does not identify a cause or point to a specific doc-kit file. Done means identifying whether doc generation is responsible and documenting a supported way to address the delay.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
JavaScript
Sterne
70
Forks
75
Ø Merge
2 T. 15 Std.
Gemergte PRs (30 T.)
48

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nodejs/doc-kit

Alle Issues in nodejs/doc-kit

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.