Skip to content

fix: terminal not exiting design mode #2593

fix: terminal not exiting design mode

fix: terminal not exiting design mode #2593

Triggered via pull request May 15, 2026 09:48
Status Failure
Total duration 1h 1m 8s
Artifacts
playwright-chromium-windows-prod
1h 1m
playwright-chromium-windows-prod
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 4 warnings, and 1 notice
playwright-chromium-windows-prod
Process completed with exit code 1.
playwright-chromium-windows-prod
Final attempt failed. Child_process exited with error code 1
playwright-chromium-windows-prod
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, nick-fields/retry@v2. 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/
playwright-chromium-windows-prod
Attempt 2 failed. Reason: Child_process exited with error code 1
playwright-chromium-windows-prod
Attempt 1 failed. Reason: Child_process exited with error code 1
playwright-chromium-windows-prod
Attempt 1 failed. Reason: Child_process exited with error code 1
playwright-chromium-windows-prod
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026