Skip to content

remove file commited by mistake #5494

remove file commited by mistake

remove file commited by mistake #5494

Triggered via pull request September 16, 2024 21:09
Status Failure
Total duration 46m 45s
Artifacts

main.yml

on: pull_request
Style check
0s
Style check
Matrix: Docker Linux Tier1
Matrix: macOS
Matrix: Windows
Fit to window
Zoom out
Zoom in

Annotations

8 errors
Windows (x86_64-pc-windows-gnu, 64, x86_64)
The hosted runner: GitHub Actions 66 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Docker Linux Tier1 (x86_64-unknown-linux-gnu)
The hosted runner: GitHub Actions 136 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
macOS (x86_64-apple-darwin)
The hosted runner: GitHub Actions 181 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Windows (x86_64-pc-windows-msvc)
The hosted runner: GitHub Actions 261 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Style check
The hosted runner: GitHub Actions 411 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Windows (i686-pc-windows-msvc)
GitHub Actions has encountered an internal error when running your job.
Docker Linux Tier1 (i686-unknown-linux-gnu)
The job was canceled because "x86_64-unknown-linux-gnu" failed.
Docker Linux Tier1 (i686-unknown-linux-gnu)
The hosted runner: GitHub Actions 477 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.