Skip to content

Use the verify_ssl option in tests #64

Use the verify_ssl option in tests

Use the verify_ssl option in tests #64

Triggered via push March 20, 2026 18:08
Status Cancelled
Total duration 1d 0h 0m 2s
Artifacts

ci.yml

on: push
Matrix: build
pre-commit
12s
pre-commit
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
build (3.11)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.13)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.6)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.8)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.10)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.12)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.7)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (3.9)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
pre-commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-python@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/