-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action jobs sometimes hang forever #6969
Comments
Jira ticket: AR-2425 |
Might be related to some improper cleanup. |
It is possible this was produced by us in past several months. |
Which umounts you had to do manually is probably the key to this. Looks to me it might be We do have code that "recursively" umounts so that definitely shouldn't happen -- the code should chase the mounts and get rid of them, no matter what -- but probably some usage has changed / is-in use during the umount / etc The key here is reproducing it, and capturing |
The funny thing is that I had to umount Best chance for reproduction is via CI since chances are way higher to hit something there. |
What happened?
Sometimes build jobs on actions runners do not complete their job and eat up resources running in circles. I noticed in increased load of journald and it seems like the stuck jobs spam the logs with stuff like
systemctl restart docker
fixes this temporary until a new job decides to get hickups.How to reproduce?
Not reproducible yet.
Noticed on both fi,mirror runnervm and littlebeast.
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Ubuntu 22.04 Jammy
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: