Skip to content

fix(tests): chromedriver path on ci #59

fix(tests): chromedriver path on ci

fix(tests): chromedriver path on ci #59

Triggered via push June 14, 2026 11:39
Status Failure
Total duration 1m 49s
Artifacts

ci.yml

on: push
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

5 errors, 3 warnings, and 1 notice
tests (windows-11-arm, 3.13.12)
The process 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' failed with exit code 1
tests (windows-11-arm, 3.13.12)
+ Throw "Error happened during Python installation" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Error happened ...on installation:String) [], RuntimeException + FullyQualifiedErrorId : Error happened during Python installation
tests (windows-11-arm, 3.13.12)
Error happened during Python installation At C:\a\_temp\c2e736ad-2b67-4beb-ad9e-f82722761f4f\setup.ps1:126 char:5
tests (windows-latest, 3.13.12)
The strategy configuration was canceled because "tests.windows-11-arm_3_13_12" failed
tests (windows-latest, 3.13.12)
The operation was canceled.
tests (ubuntu-latest, 3.13.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, browser-actions/setup-chrome@v2.1.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
tests (windows-11-arm, 3.13.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: browser-actions/setup-chrome@v2.1.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
tests (windows-latest, 3.13.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, browser-actions/setup-chrome@v2.1.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
tests (windows-latest, 3.13.12)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026