Process completed with exit code 2.

--- stderr --- node:internal/modules/run_main:107 triggerUncaughtException( ^ AssertionError [ERR_ASSERTION]: should support relative specifiers with single quotes at async file:///home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs:26:1 { generatedMessage: false, code: 'ERR_ASSERTION', actual: ReferenceError: RegExpPrototypeSymbolReplace is not defined at #asyncInstantiate (node:internal/modules/esm/module_job:427:43) at async ModuleJob.run (node:internal/modules/esm/module_job:500:5) at async node:internal/modules/esm/loader:716:26 at async assert.rejects.name (file:///home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs:27:3) at async waitForActual (node:assert:615:5) at async assert.rejects (node:assert:738:25) at async file:///home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs:26:1, expected: { name: 'SyntaxError', message: "Named export 'comeOn' not found. The requested module './fail.cjs' is a CommonJS module, which may not support all module.exports as named exports.\n" + 'CommonJS modules can always be imported via the default export, for example using:\n' + '\n' + "import pkg from './fail.cjs';\n" + 'const { comeOn } = pkg;\n' }, operator: 'rejects', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node /home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs

--- stderr --- node:internal/assert/utils:146 throw error; ^ AssertionError [ERR_ASSERTION]: These builtins are now unexpectedly loaded before pre-execution. If this is intentional, add them to `expected.beforePreExec`. # Note: loading more builtins before pre-execution can lead to startup performance regression or invalid snapshots. - Consider lazy loading builtins that are not used universally. - Make sure that the builtins do not access environment dependent states e.g. command line arguments or environment variables during loading. - When in doubt, ask @nodejs/startup. --- These could be added to expected.beforePreExec --- [ 'NativeModule internal/errors/error_source' ] 9 !== 0 at Object.<anonymous> (/home/runner/work/node/node/node/test/parallel/test-bootstrap-modules.js:264:8) at Module._compile (node:internal/modules/cjs/loader:1888:14) at Object..js (node:internal/modules/cjs/loader:2030:10) at Module.load (node:internal/modules/cjs/loader:1611:32) at Module._load (node:internal/modules/cjs/loader:1358:12) at wrapModuleLoad (node:internal/modules/cjs/loader:259:19) at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5) at node:internal/main/run_main_module:33:47 { generatedMessage: false, code: 'ERR_ASSERTION', actual: 9, expected: 0, operator: 'strictEqual', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node /home/runner/work/node/node/node/test/parallel/test-bootstrap-modules.js

Process completed with exit code 2.

--- stderr --- node:internal/assert/utils:146 throw error; ^ AssertionError [ERR_ASSERTION]: These builtins are now unexpectedly loaded before pre-execution. If this is intentional, add them to `expected.beforePreExec`. # Note: loading more builtins before pre-execution can lead to startup performance regression or invalid snapshots. - Consider lazy loading builtins that are not used universally. - Make sure that the builtins do not access environment dependent states e.g. command line arguments or environment variables during loading. - When in doubt, ask @nodejs/startup. --- These could be added to expected.beforePreExec --- [ 'NativeModule internal/errors/error_source' ] 9 !== 0 at Object.<anonymous> (/home/runner/work/node/node/node/test/parallel/test-bootstrap-modules.js:264:8) at Module._compile (node:internal/modules/cjs/loader:1888:14) at Object..js (node:internal/modules/cjs/loader:2030:10) at Module.load (node:internal/modules/cjs/loader:1611:32) at Module._load (node:internal/modules/cjs/loader:1358:12) at wrapModuleLoad (node:internal/modules/cjs/loader:259:19) at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5) at node:internal/main/run_main_module:33:47 { generatedMessage: false, code: 'ERR_ASSERTION', actual: 9, expected: 0, operator: 'strictEqual', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node /home/runner/work/node/node/node/test/parallel/test-bootstrap-modules.js

--- stderr --- node:internal/modules/run_main:107 triggerUncaughtException( ^ AssertionError [ERR_ASSERTION]: should support relative specifiers with single quotes at async file:///home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs:26:1 { generatedMessage: false, code: 'ERR_ASSERTION', actual: ReferenceError: RegExpPrototypeSymbolReplace is not defined at #asyncInstantiate (node:internal/modules/esm/module_job:427:43) at async ModuleJob.run (node:internal/modules/esm/module_job:500:5) at async node:internal/modules/esm/loader:716:26 at async assert.rejects.name (file:///home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs:27:3) at async waitForActual (node:assert:615:5) at async assert.rejects (node:assert:738:25) at async file:///home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs:26:1, expected: { name: 'SyntaxError', message: "Named export 'comeOn' not found. The requested module './fail.cjs' is a CommonJS module, which may not support all module.exports as named exports.\n" + 'CommonJS modules can always be imported via the default export, for example using:\n' + '\n' + "import pkg from './fail.cjs';\n" + 'const { comeOn } = pkg;\n' }, operator: 'rejects', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node /home/runner/work/node/node/node/test/es-module/test-esm-cjs-named-error.mjs

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Mozilla-Actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Mozilla-Actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

73% - 3618 hits, 1344 misses, 0 errors