Skip to content

Correct path of cgroup when running a container in a container #215

Correct path of cgroup when running a container in a container

Correct path of cgroup when running a container in a container #215

Re-run triggered April 15, 2024 01:21
Status Failure
Total duration 14s
Artifacts

commit-message-check.yaml

on: pull_request
Commit Message Check
4s
Commit Message Check
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Commit Message Check
8c1968799b41ad739bec42d465bdabe63e1989b6 Commit body is missing
Commit Message Check
The SoB (DCO) check failed 8c1968799b41ad739bec42d465bdabe63e1989b6 The sign-off is missing. What should I do to fix it ? All proposed commits should include a Signed-Off-By: <your-email-address> line in their commit message. This is most conveniently done by using --signoff (-s) when running git commit.
Commit Message Check
8c1968799b41ad739bec42d465bdabe63e1989b6 Body line too long (max 72) See the document below for help on formatting commits for the project. https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md#patch-forma
Commit Message Check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: tim-actions/get-pr-commits@v1.0.0, tim-actions/dco@2fd0504dc0d27b33f542867c300c60840c6dcb20, tim-actions/commit-body-check@v1.0.2, tim-actions/commit-message-checker-with-regex@v0.3.1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Commit Message Check
The following actions uses node12 which is deprecated and will be forced to run on node16: tim-actions/get-pr-commits@v1.0.0, tim-actions/dco@2fd0504dc0d27b33f542867c300c60840c6dcb20, tim-actions/commit-body-check@v1.0.2, tim-actions/commit-message-checker-with-regex@v0.3.1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Commit Message Check
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/