JRuby Continuous Integration #383
tannalynn
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci_jruby.yml
on: schedule
unit_tests
4m 31s
Matrix: jruby_multiverse
Annotations
12 errors
|
jruby_multiverse (background)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
jruby_multiverse (background)
The operation was canceled.
|
|
jruby_multiverse (background_2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
jruby_multiverse (background_2)
The operation was canceled.
|
|
jruby_multiverse (frameworks)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
jruby_multiverse (frameworks)
The operation was canceled.
|
|
jruby_multiverse (agent)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
jruby_multiverse (agent)
The operation was canceled.
|
|
jruby_multiverse (database)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
jruby_multiverse (database)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
jruby_multiverse (rails)
The hosted runner: GitHub Actions 37 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.
|
|
jruby_multiverse (httpclients)
The hosted runner: GitHub Actions 26 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.
|