Page MenuHomePhabricator

Unsupported node engine in REL1_39
Closed, InvalidPublic

Description

https://integration.wikimedia.org/ci/job/mediawiki-quibble-composer-mysql-php82/74/console

10:12:39 npm WARN EBADENGINE Unsupported engine {
10:12:39 npm WARN EBADENGINE   package: '@es-joy/jsdoccomment@0.20.1',
10:12:39 npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16 || ^17' },
10:12:39 npm WARN EBADENGINE   current: { node: 'v18.20.2', npm: '10.5.0' }
10:12:39 npm WARN EBADENGINE }
10:12:39 npm WARN EBADENGINE Unsupported engine {
10:12:39 npm WARN EBADENGINE   package: 'eslint-plugin-jsdoc@37.9.4',
10:12:39 npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16 || ^17' },
10:12:39 npm WARN EBADENGINE   current: { node: 'v18.20.2', npm: '10.5.0' }
10:12:39 npm WARN EBADENGINE }

Seemingly only in PHP8.2 jobs?

Event Timeline

Reedy triaged this task as High priority.May 13 2024, 9:22 AM
Reedy updated the task description. (Show Details)

I usually ignore these warnings; the actual error in that build seems to have been something else:

npm ERR! code EEXIST
npm ERR! syscall open
npm ERR! path /cache/npm/_cacache/tmp/efacacda
npm ERR! errno -17
npm ERR! EEXIST: file already exists, open '/cache/npm/_cacache/tmp/efacacda'
npm ERR! File exists: /cache/npm/_cacache/tmp/efacacda
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

which is an error that happens from time to time (T300018 and maybe other tasks, not sure; may or may not be the same cause as T295351).

Yeah, the npm WARN isn't fatalling here, it's just a regular npm cache CI miss/disc-lock issue. Invalid?