Skip to content
CI

Don't install Tapioca and its dependencies on Ruby 3.1 #14833

Sign in to view logs

Don't install Tapioca and its dependencies on Ruby 3.1

Don't install Tapioca and its dependencies on Ruby 3.1 #14833

Triggered via push May 22, 2025 08:55
@st0012st0012
pushed 15cb5f4
bump-tapioca-and-sorbet
Status Failure
Total duration 45m 15s
Artifacts –

ci.yml

on: push
spelling
0s
spelling
lint_ruby
30s
lint_ruby
lint_node
41s
lint_node
Verify Jekyll website builds
0s
Verify Jekyll website builds
Matrix: build_node
Matrix: build_ruby
Fit to window
Zoom out
Zoom in

Annotations

7 errors
Ruby 3.1 on macos-latest
The process '/Users/runner/hostedtoolcache/Ruby/3.1.7/arm64/bin/bundle' failed with exit code 6
spelling
The hosted runner: GitHub Actions 1377 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.
Verify Jekyll website builds
The hosted runner: GitHub Actions 629 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.
build_node (ubuntu-latest)
The hosted runner: GitHub Actions 143 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.
build_node (macos-latest)
The hosted runner: GitHub Actions 715 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.
Ruby 3.1 on windows-latest
The hosted runner: GitHub Actions 1025 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.
Ruby 3.1 on ubuntu-latest
The hosted runner: GitHub Actions 995 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.