`node-gyp` fails in all current variants

[MikeMcC399]

• relates to Review all tests #1136

Situation

Running citgm node-gyp fails all tests
macos/ubuntu/windows
Node.js 22/24/26

Steps to reproduce

Run https://github.com/nodejs/citgm/actions/workflows/test-module.yml

Module to test: node-gyp
CITGM repository to checkout: nodejs/citgm
CITGM GitHub ref to checkout: main

Result

Fails all current variants:

Node.js	npm	macos	ubuntu	windows
22.23.3	10.9.9	FAIL	FAIL	FAIL
24.21.0	11.19.0	FAIL	FAIL	FAIL
26.10.0	11.19.1	FAIL	FAIL	FAIL

Run node bin/citgm.js node-gyp
info: starting            | node-gyp
info: lookup              | node-gyp
info: lookup-found        | node-gyp
info: node-gyp lookup-replace| https://github.com/nodejs/node-gyp/archive/HEAD.tar.gz
info: node-gyp npm:       | Downloading project: https://github.com/nodejs/node-gyp/archive/HEAD.tar.gz
info: node-gyp npm:       | Project downloaded HEAD.tar.gz
info: node-gyp npm:       | npm install started
info: node-gyp npm:       | npm install successfully completed
info: node-gyp npm:       | test suite started
error: failure             | The canary is dead:
error: failing module(s)   |
error: module name:        | node-gyp
error: version:            | 13.0.2
error: error:              | The canary is dead:
error: error:              | undefined
error:                     | added 277 packages in 10s

References

citgm/lib/lookup.json

Lines 321 to 327 in 4d3d256

	"node-gyp": {
	"envVar": { "FAST_TEST": "true" },
	"tags": "native",
	"maintainers": ["nodejs/node-gyp"],
	"skip": ["win32"],
	"head": true
	},

https://github.com/nodejs/node-gyp
https://github.com/nodejs/node-gyp/releases
https://github.com/nodejs/node-gyp/releases/tag/v13.0.2

cc: @nodejs/node-gyp

[gengjiawen]

Thanks for the report! This is a node-gyp regression that only shows up because of citgm's environment.

citgm sets npm_config_loglevel (default error) for the module's npm test (create-options.js#L16). Since nodejs/node-gyp#3196 (v11.4.0), node-gyp lets that environment variable override an explicit --loglevel on the command line. As a result, the addon tests (which pass --loglevel=verbose) never print gyp info ok, and the shared logger is already at error when options in environment runs. npm_config_loglevel=error npm test reproduces exactly these 3 failures locally.

Fix: nodejs/node-gyp#3384. Since the lookup uses "head": true, citgm node-gyp should go green as soon as it lands, with no release needed.

Side note: the Windows jobs only fail on the same 3 tests, even though the lookup has "skip": ["win32"]. That's because skip is only honored by citgm-all, not single-module runs.

[MikeMcC399]

Hi @gengjiawen

Thank you very much for taking a look at this issue and proposing a fix in nodejs/node-gyp#3384. Much appreciated! 👍

[MikeMcC399]

node-gyp@13.1.0, released Oct 2, 2026, passes all variants:

Node.js	npm	macos	ubuntu	windows
22.23.3	10.9.9	PASS	PASS	PASS
24.21.0	11.19.0	PASS	PASS	PASS
26.10.0	11.19.1	PASS	PASS	PASS

This issue can now be closed.