rspack-ecosystem-ci-from-commit #67
fi3eworkrspack-ecosystem-ci-from-commit.yml
on: workflow_dispatch
Get Runner Labels
/
Get Runner Labels
4s
execute-all (${{ inputs.suite }})
0s
Matrix: execute-all
Annotations
25 errors and 14 warnings
|
execute-all (examples)
Process completed with exit code 1.
|
|
execute-all (lynx-stack)
Process completed with exit code 1.
|
|
execute-all (lynx-stack)
@lynx-js/devtool-connector#build: command (/tmp/lynx-stack-jyu0l2/lynx-stack/packages/mcp-servers/devtool-connector) /opt/hostedtoolcache/node/22.22.2/x64/bin/pnpm run build exited (1)
|
|
css-extract/TestCases.test.js > TestCases > at-media should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCases.test.js > TestCases > at-import-supports should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCases.test.js > TestCases > at-import-layer should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCases.test.js > TestCases > at-import-in-the-middle should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCases.test.js > TestCases > at-import should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCases.test.js > TestCases > at-charset should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCases.test.js > TestCases > asset-modules should compile to the expected result:
workspace/plugin/rspack-plugin-ci/css-extract/TestCases.test.js#L201
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCache.test.js > TestCache > should work with the "memory" cache:
workspace/plugin/rspack-plugin-ci/css-extract/TestCache.test.js#L118
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/TestCache.test.js > TestCache > should work without cache:
workspace/plugin/rspack-plugin-ci/css-extract/TestCache.test.js#L18
Cannot read properties of undefined (reading 'meta')
|
|
css-extract/HMR.test.js >:
workspace/plugin/rspack-plugin-ci/css-extract/HMR.test.js#L10
Cannot read properties of undefined (reading 'meta')
|
|
execute-all (rslib)
Process completed with exit code 1.
|
|
tests/integration/polyfill/index.test.ts > polyfill > should polyfill in CJS:
workspace/rslib/rslib/tests/integration/polyfill/index.test.ts#L27
Cannot read properties of undefined (reading 'meta')
|
|
tests/integration/polyfill/index.test.ts > polyfill > should polyfill in ESM:
workspace/rslib/rslib/tests/integration/polyfill/index.test.ts#L18
Cannot read properties of undefined (reading 'meta')
|
|
tests/integration/node-polyfill/index.test.ts > `Buffer` should be aliased to polyfill packages when bundle is disabled:
workspace/rslib/rslib/tests/integration/node-polyfill/index.test.ts#L55
Cannot read properties of undefined (reading 'meta')
|
|
tests/integration/node-polyfill/index.test.ts > `Buffer` should be imported from polyfill when bundled:
workspace/rslib/rslib/tests/integration/node-polyfill/index.test.ts#L13
Cannot read properties of undefined (reading 'meta')
|
|
tests/integration/externals/index.test.ts > require ESM from CJS:
workspace/rslib/rslib/tests/integration/externals/index.test.ts#L148
Cannot read properties of undefined (reading 'meta')
|
|
tests/integration/bundle-false/index.test.ts > basic:
workspace/rslib/rslib/tests/integration/bundle-false/index.test.ts#L97
Cannot read properties of undefined (reading 'meta')
|
|
tests/integration/shims/index.test.ts >:
workspace/rslib/rslib/tests/integration/shims/index.test.ts#L12
Cannot read properties of undefined (reading 'meta')
|
|
execute-all (rstest)
Process completed with exit code 1.
|
|
test-api/json.test.ts > should test json file correctly:
workspace/rstest/rstest/e2e/test-api/json.test.ts#L11
expected { value%3A 123%2C default%3A { value%3A 123 } } to deeply equal { __esModule%3A true%2C value%3A 123%2C …(1)%2C …(1) }
Compared values have no visual difference.
|
|
test-api/json.test.ts > should test json file correctly:
workspace/rstest/rstest/e2e/test-api/json.test.ts#L11
expected { value%3A 123%2C default%3A { value%3A 123 } } to deeply equal { __esModule%3A true%2C value%3A 123%2C …(1)%2C …(1) }
Compared values have no visual difference.
|
|
test-api/json.test.ts > should test json file correctly:
workspace/rstest/rstest/e2e/test-api/json.test.ts#L11
expected { value%3A 123%2C default%3A { value%3A 123 } } to deeply equal { __esModule%3A true%2C value%3A 123%2C …(1)%2C …(1) }
Compared values have no visual difference.
|
|
Prepare Rspack Binding
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4. 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/
|
|
execute-all (_selftest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (examples)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (lynx-stack)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (plugin)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (rsbuild-rsc-plugin)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (rsbuild)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (devserver)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (rslib)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (rsdoctor)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (rstest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (rspress)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (modernjs)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, crazy-max/ghaction-github-runtime@v3. 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/
|
|
execute-all (modernjs)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
binding-linux-x64-gnu
|
109 MB |
sha256:d315c7bca83f33693862d6ff664b14ceaa297c4b83722c2177becfd290d19589
|
|