298.2 actions checkout error
See original GitHub issueDescribe the bug
Error: Command failed: rm -rf “/home/docker/actions-runner/_work/assignment-2-mishasinitcyn/assignment-2-mishasinitcyn/.git” rm: cannot remove ‘/home/docker/actions-runner/_work/assignment-2-mishasinitcyn/assignment-2-mishasinitcyn/.git/hooks’: Directory not empty rm: cannot remove ‘/home/docker/actions-runner/_work/assignment-2-mishasinitcyn/assignment-2-mishasinitcyn/.git/info’: Directory not empty rm: cannot remove ‘/home/docker/actions-runner/_work/assignment-2-mishasinitcyn/assignment-2-mishasinitcyn/.git/refs/remotes/origin’: Directory not empty rm: cannot remove ‘/home/docker/actions-runner/_work/assignment-2-mishasinitcyn/assignment-2-mishasinitcyn/.git/objects/pack’: Directory not empty rm: cannot remove ‘/home/docker/actions-runner/_work/assignment-2-mishasinitcyn/assignment-2-mishasinitcyn/.git/logs/refs/remotes/origin’: Directory not empty
(node:84696) UnhandledPromiseRejectionWarning: Error: Command failed: rm -rf “/home/docker/actions-runner/_work/_temp/e977c0c9-2d91-458e-8cc5-c37ffd11e877” rm: cannot remove ‘/home/docker/actions-runner/_work/_temp/e977c0c9-2d91-458e-8cc5-c37ffd11e877’: Directory not empty
at ChildProcess.exithandler (child_process.js:308:12)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1022:16)
at Socket.<anonymous> (internal/child_process.js:444:11)
at Socket.emit (events.js:314:20)
at Pipe.<anonymous> (net.js:675:12)
(node:145) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:145) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to ‘…’
- Run ‘…’
- See error
Expected behavior A clear and concise description of what you expected to happen.
Runner Version and Platform
Version of your runner? 298.2 OS of the machine running the runner? OSX/Windows/Linux/… Linux (actions running inside docker)
What’s not working?
Please include error messages and screenshots.
at ChildProcess.exithandler (child_process.js:308:12)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1022:16)
at Socket.<anonymous> (internal/child_process.js:444:11)
at Socket.emit (events.js:314:20)
at Pipe.<anonymous> (net.js:675:12)
(node:145) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:145) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker’s Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner’s _diag
folder. The runner logs are prefixed with Runner_
and the worker logs are prefixed with Worker_
. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
I will give this a shot and also set up a public repo that you can investigate on. Thanks
I will close this issue until we hear back from you. If you discover that the issue is not occurring for the reason I wrote above, feel free to re-open the issue, and please do provide the repo, so we can re-produce it.