build: skip dockit on riscv64

[sxa]

The doc-only target gives a variety of failures on different riscv64 systems. These symptoms are described in nodejs/build#4099 (comment) in the section Additional info on the Wasm doc-only crash

This removes the doc-only target from being run by default as part of make test-ci similar to what has been done for AIX and IBMi.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.05%. Comparing base (f9ab994) to head (268522b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #62251      +/-   ##
==========================================
- Coverage   90.07%   90.05%   -0.02%     
==========================================
  Files         754      754              
  Lines      256395   256395              
  Branches    48494    48498       +4     
==========================================
- Hits       230947   230897      -50     
- Misses      16563    16615      +52     
+ Partials     8885     8883       -2     

see 26 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kxxt]

I think we can fix it (at least the WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance part) by bumping @nodejs/doc-kit after nodejs/doc-kit#691 is merged.

[kxxt]

by bumping @nodejs/doc-kit after nodejs/doc-kit#691 is merged.

#62686

[sxa]

Probably fixed with the updae in #62512 - running a test on my K1 at https://ci.nodejs.org/job/sxa-rvnodetest/399/

[sxa]

Noting that I hit this again today with a branch that had the doc-kit 1.4.1 added in https://github.com/nodejs/node/pull/64010/changes so this may still be required.

0:52:24 cp -r doc/api out/doc
20:52:25 npm warn cli npm v11.17.0 does not support Node.js v26.5.1-pre. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
20:52:36 
20:52:36 added 280 packages, and audited 282 packages in 11s
20:52:36 
20:52:36 137 packages are looking for funding
20:52:36   run `npm fund` for details
20:52:36 
20:52:36 1 moderate severity vulnerability
20:52:36 
20:52:36 To address all issues, run:
20:52:36   npm audit fix
20:52:36 
20:52:36 Run `npm audit` for details.
20:53:25 [19:53:25.175] ERROR: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
20:53:25 RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance

Ref: https://ci.nodejs.org/job/sxa-node-test-commit-rvlinux/14/nodes=riscv64

[sxa]

Apparently the variable name in this PR didn't work for the check - changed from DESTCPU to ARCHTYPE which is the variable used for detecting arm64 elsewhere in the Makefile.

[sxa]

request-ci hasn't taken effect - triggered manually at https://ci.nodejs.org/job/node-test-pull-request/76624

Noting that the request-ci triggers have been playing up. Ref: nodejs/build#4443

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76624/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76648/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76727/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76810/ (retry - no smartos)

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76811/ (build - no smartos)

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76812/ (resume)

[sxa]

Force pushing to squash since no-one has reviewed yet and to rebase - no changes to what was in this PR earlier.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76834/

[sxa]

Dropping to draft again while some further testing occurs to prevent anyone merging this for now but noting that we're still getthing this error, albeit ignored and so it doesn't prevent the build from continuing.

18:56:06   ln -fs out/Release/node node; fi
18:56:16 Illegal instruction
18:56:16 make: [Makefile:886: out/doc/api/addons.html] Error 132 (ignored)