Skip to content

Bump up 5.1.2

Bump up 5.1.2 #56

Triggered via push December 19, 2023 02:06
Status Failure
Total duration 49m 2s
Artifacts

test.yml

on: push
ruby-versions  /  Generate Ruby versions
3s
ruby-versions / Generate Ruby versions
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

8 errors
test (2.5, macos-latest)
The hosted runner: GitHub Actions 6 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 (2.6, macos-latest)
The hosted runner: GitHub Actions 36 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 (3.1, macos-latest)
The hosted runner: GitHub Actions 45 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 (3.2, macos-latest)
The hosted runner: GitHub Actions 48 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 (2.7, macos-latest)
The hosted runner: GitHub Actions 39 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 (head, macos-latest)
The hosted runner: GitHub Actions 52 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 (jruby-head, macos-latest)
The hosted runner: GitHub Actions 58 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 (jruby, macos-latest)
The hosted runner: GitHub Actions 54 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.