Update changelog for 8.1.8 #282
kitchen-porterci.yml
on: push
lint-unit
/
rspec
37s
lint-unit
/
cookstyle
34s
lint-unit
/
yamllint
9s
lint-unit
/
markdownlint-cli2
3s
lint-unit
/
markdown-link-check
16s
lint-unit
/
check-metadata
0s
Matrix: integration
Annotations
14 errors
|
integration (centos-7, default)
The process '/usr/bin/kitchen' failed with exit code 1
|
|
integration (centos-stream-8, default)
The process '/usr/bin/kitchen' failed with exit code 1
|
|
integration (ubuntu-1804, default)
The process '/usr/bin/kitchen' failed with exit code 1
|
|
integration (debian-10, default)
The process '/usr/bin/kitchen' failed with exit code 1
|
|
integration (ubuntu-2004, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
integration (ubuntu-2004, default)
The hosted runner: GitHub Actions 21 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.
|
|
integration (amazonlinux-2, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
integration (amazonlinux-2, default)
The hosted runner: GitHub Actions 12 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.
|
|
integration (rockylinux-8, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
integration (rockylinux-8, default)
The operation was canceled.
|
|
integration (almalinux-8, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
integration (almalinux-8, default)
The hosted runner: GitHub Actions 25 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.
|
|
integration (fedora-latest, default)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
integration (fedora-latest, default)
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.
|