Skip to content
Release Build

fix sql fmt (#134) #157

Sign in to view logs

fix sql fmt (#134)

fix sql fmt (#134) #157

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

release.yml

on: push
Matrix: Release Build
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Release Build (ubuntu-latest, 1.77.2)
The hosted runner: GitHub Actions 20 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.
Release Build (macos-latest, 1.77.2)
The hosted runner: GitHub Actions 5 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.
Release Build (macos-latest, stable)
The hosted runner: GitHub Actions 11 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.
Release Build (windows-latest, 1.77.2)
The hosted runner: GitHub Actions 10 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.
Release Build (ubuntu-latest, stable)
The hosted runner: GitHub Actions 8 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.
Release Build (windows-latest, stable)
The hosted runner: GitHub Actions 4 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.