Skip to content

chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 #7110

chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11

chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 #7110

Triggered via pull request October 7, 2024 06:06
Status Failure
Total duration 54m 25s
Artifacts

testing.yml

on: pull_request
Documentation
3m 13s
Documentation
Long tests on Python 3.10
42m 25s
Long tests on Python 3.10
Tests that may fail due to network or HTML
43m 39s
Tests that may fail due to network or HTML
Windows long tests
7m 21s
Windows long tests
Matrix: Linux tests
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Windows long tests
Process completed with exit code 1.
Tests that may fail due to network or HTML
The self-hosted runner: ephemeral-action-runner-ubuntu-2404-i-0bc2d534578b6e2d1 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Long tests on Python 3.10
The self-hosted runner: ephemeral-action-runner-ubuntu-2404-i-06e2bdc78a64fb46c lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Linux tests (3.8)
The self-hosted runner: ephemeral-action-runner-ubuntu-2404-i-0fdeef4ed3aa5aecc lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Linux tests (3.9)
The job was canceled because "_3_8" failed.
Linux tests (3.9)
The self-hosted runner: ephemeral-action-runner-ubuntu-2404-i-0711b03d08f6b7892 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.