rspack-ecosystem-ci-from-commit #240
rspack-ecosystem-ci-from-commit.yml
on: workflow_dispatch
Get Runner Labels
/
Get Runner Labels
2s
execute-all (${{ inputs.suite }})
0s
Matrix: execute-all
Annotations
13 errors and 13 warnings
|
execute-all (_selftest)
Process completed with exit code 1.
|
|
execute-all (lynx-stack)
Process completed with exit code 1.
|
|
execute-all (lynx-stack)
@lynx-js/tailwind-preset#build: command (/tmp/lynx-stack-L2lvBl/lynx-stack/packages/tailwind-preset) /opt/hostedtoolcache/node/22.22.2/x64/bin/pnpm run build exited (1)
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support inject first screen css:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.root-layout` failed
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support redirect on first screen load:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.user-page-data-container` failed
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support redirect on first screen load:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.user-page-data-container` failed
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support direct redirect navigation:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/api/ElementHandle.ts#L507
Error%3A failed to find element matching selector ".root-page"
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support direct redirect navigation:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/api/ElementHandle.ts#L507
Error%3A failed to find element matching selector ".root-page"
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support route as client component and navigation:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.root-page` failed
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support route as client component and navigation:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.root-page` failed
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support route as server component and client component:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.user-page-data-container` failed
|
|
integration/rsc-csr-routes/tests/index.test.ts > dev > csr-rsc-routes-with-loader > support route as server component and client component:
file:///home/runner/work/rstack-ecosystem-ci/rstack-ecosystem-ci/workspace/modernjs/modern.js/node_modules/.pnpm/puppeteer-core@24.39.1_bufferutil@4.1.0_utf-8-validate@5.0.10/node_modules/puppeteer-core/src/common/QueryHandler.ts#L213
Waiting for selector `.user-page-data-container` failed
|
|
integration/ssr/tests/rsc-closing-tags.test.ts >:
workspace/modernjs/modern.js/tests/integration/ssr/tests/rsc-closing-tags.test.ts#L41
expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
|
|
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/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/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/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/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/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/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/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/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/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/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/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/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/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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
binding-linux-x64-gnu
|
108 MB |
sha256:32cde51c9e5fb0f0db934d84acb79d3616d3c6179cc6b84b5acc00de8be97812
|
|