Skip to content
Test

fix sql fmt (#134) #173

Sign in to view logs

fix sql fmt (#134)

fix sql fmt (#134) #173

Triggered via push September 16, 2024 21:14
@neonphogneonphog
pushed 6bbd604
main
Status Failure
Total duration 48m 17s
Artifacts –

test.yml

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

Annotations

6 errors
Test (macos-latest, 1.77.2)
The hosted runner: GitHub Actions 2 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.
Test (macos-latest, stable)
The hosted runner: GitHub Actions 1 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.
Test (ubuntu-latest, stable)
The hosted runner: GitHub Actions 17 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.
Test (ubuntu-latest, 1.77.2)
The hosted runner: GitHub Actions 16 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.
Test (windows-latest, stable)
The hosted runner: GitHub Actions 14 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.
Test (windows-latest, 1.77.2)
The hosted runner: GitHub Actions 3 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.