Skip to content

fix: arbiter quality D→A — complexity, vulture excludes, dedup (#3) #19

fix: arbiter quality D→A — complexity, vulture excludes, dedup (#3)

fix: arbiter quality D→A — complexity, vulture excludes, dedup (#3) #19

Triggered via push March 29, 2026 13:59
Status Failure
Total duration 20s
Artifacts

ci.yml

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

Annotations

4 errors and 1 warning
test (3.12)
The process 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' failed with exit code 1
test (3.12)
because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170. At line:1 char:1 + ./setup.ps1 + ~~~~~~~~~~~ + CategoryInfo : SecurityError: (:) [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess
test (3.12)
./setup.ps1 : File C:\actions-runner\_work\_temp\8f173c64-d49f-40ea-87bb-41436738e81c\setup.ps1 cannot be loaded
test (3.11)
The strategy configuration was canceled because "test._3_12" failed
test (3.12)
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/setup-python@v5. 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/