Skip to content

Virtual File System for Node.js #4425

Virtual File System for Node.js

Virtual File System for Node.js #4425

Triggered via pull request March 19, 2026 18:34
Status Failure
Total duration 42m 1s
Artifacts 1

test-shared.yml

on: pull_request
Build slim tarball
1m 58s
Build slim tarball
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 4 warnings
aarch64-linux: with shared libraries
Process completed with exit code 2.
aarch64-linux: with shared libraries: test/parallel/test-vfs-module-hooks.mjs#L0
--- stderr --- node:internal/vfs/setup:1163 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /mh28/bad-json-dir/package.json. Expected property name or '}' in JSON at position 2 (line 1 column 3) at readPackageJSON (node:internal/vfs/setup:1163:19) at loaderReadPackageJSON (node:internal/modules/helpers:181:12) at Object.read (node:internal/modules/package_json_reader:130:18) at _readPackage (node:internal/modules/cjs/loader:506:55) at tryPackage (node:internal/modules/cjs/loader:527:36) at Module._findPath (node:internal/modules/cjs/loader:809:18) at Module._resolveFilename (node:internal/modules/cjs/loader:1471:27) at wrapResolveFilename (node:internal/modules/cjs/loader:1059:27) at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1083:10) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1104:12) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v26.0.0-pre Command: out/Release/node /home/runner/work/_temp/node-v26.0.0-nightly2026-03-198f8b79aafc-slim/test/parallel/test-vfs-module-hooks.mjs
aarch64-darwin: with shared libraries
Process completed with exit code 2.
aarch64-darwin: with shared libraries: test/parallel/test-vfs-module-hooks.mjs#L0
--- stderr --- node:internal/vfs/setup:1163 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /mh28/bad-json-dir/package.json. Expected property name or '}' in JSON at position 2 (line 1 column 3) at readPackageJSON (node:internal/vfs/setup:1163:19) at loaderReadPackageJSON (node:internal/modules/helpers:181:12) at Object.read (node:internal/modules/package_json_reader:130:18) at _readPackage (node:internal/modules/cjs/loader:506:55) at tryPackage (node:internal/modules/cjs/loader:527:36) at Module._findPath (node:internal/modules/cjs/loader:809:18) at Module._resolveFilename (node:internal/modules/cjs/loader:1471:27) at wrapResolveFilename (node:internal/modules/cjs/loader:1059:27) at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1083:10) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1104:12) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v26.0.0-pre Command: out/Release/node /Users/runner/work/_temp/node-v26.0.0-nightly2026-03-198f8b79aafc-slim/test/parallel/test-vfs-module-hooks.mjs
x86_64-linux: with shared libraries
Process completed with exit code 2.
x86_64-linux: with shared libraries: test/parallel/test-vfs-module-hooks.mjs#L0
--- stderr --- node:internal/vfs/setup:1163 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /mh28/bad-json-dir/package.json. Expected property name or '}' in JSON at position 2 (line 1 column 3) at readPackageJSON (node:internal/vfs/setup:1163:19) at loaderReadPackageJSON (node:internal/modules/helpers:181:12) at Object.read (node:internal/modules/package_json_reader:130:18) at _readPackage (node:internal/modules/cjs/loader:506:55) at tryPackage (node:internal/modules/cjs/loader:527:36) at Module._findPath (node:internal/modules/cjs/loader:809:18) at Module._resolveFilename (node:internal/modules/cjs/loader:1471:27) at wrapResolveFilename (node:internal/modules/cjs/loader:1059:27) at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1083:10) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1104:12) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v26.0.0-pre Command: out/Release/node /home/runner/work/_temp/node-v26.0.0-nightly2026-03-198f8b79aafc-slim/test/parallel/test-vfs-module-hooks.mjs
x86_64-darwin: with shared libraries
Process completed with exit code 2.
x86_64-darwin: with shared libraries: test/parallel/test-vfs-module-hooks.mjs#L0
--- stderr --- node:internal/vfs/setup:1163 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /mh28/bad-json-dir/package.json. Expected property name or '}' in JSON at position 2 (line 1 column 3) at readPackageJSON (node:internal/vfs/setup:1163:19) at loaderReadPackageJSON (node:internal/modules/helpers:181:12) at Object.read (node:internal/modules/package_json_reader:130:18) at _readPackage (node:internal/modules/cjs/loader:506:55) at tryPackage (node:internal/modules/cjs/loader:527:36) at Module._findPath (node:internal/modules/cjs/loader:809:18) at Module._resolveFilename (node:internal/modules/cjs/loader:1471:27) at wrapResolveFilename (node:internal/modules/cjs/loader:1059:27) at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1083:10) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1104:12) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v26.0.0-pre Command: out/Release/node /Users/runner/work/_temp/node-v26.0.0-nightly2026-03-198f8b79aafc-slim/test/parallel/test-vfs-module-hooks.mjs
aarch64-linux: with shared libraries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
aarch64-darwin: with shared libraries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
x86_64-linux: with shared libraries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
x86_64-darwin: with shared libraries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
tarballs
48.6 MB
sha256:49ad9b944be006300dbfe23bed24f909c022358996a7e64efadb14049bfd6b3c