Skip to content

fix: resolve navigation hang on Windows when using intercept with object mock #4174

fix: resolve navigation hang on Windows when using intercept with object mock

fix: resolve navigation hang on Windows when using intercept with object mock #4174

Re-run triggered April 28, 2026 11:25
Status Failure
Total duration 5m 8s
Artifacts

taiko.yml

on: pull_request
Matrix: unit-tests
Matrix: docs-tests
Matrix: functional-tests-headful
Matrix: functional-tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Unit tests - windows-latest - 24
Final attempt failed. Child_process exited with error code 1
Unit tests - windows-latest - 24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@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/
Unit tests - windows-latest - 24
Attempt 1 failed. Reason: Child_process exited with error code 1
Unit tests - windows-latest - 24
Could not determine the Biome version from the project files. Falling back to the latest version. If this is unexpected, make sure your repository has been checked out and that the working-dir input is set to the directory containing your project (defaults to the root of the repository).