-
Notifications
You must be signed in to change notification settings - Fork 523
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
Long post job cleanup #431
Comments
Hello, @fat-fellow! Thank you for reporting this issue, we will investigate it and see what can be done :) |
Hello @fat-fellow, the caching makes little sense on the self-hosted runner because the persists the build state between runs. I advise to disable the caching:
did it help? |
I have the same problem, I've run it twice now, one time it skipped the tar process (which is what takes all the time) and one time it did not. I will keep trying it. thanks for the tip. |
@nixomose do you have a problem with self-hosted environment as well? |
yeah, when you run the setup go action on a self hosted linux machine, the cleanup step tars up some go directories and it takes a few seconds. |
@nixomose caching makes little if any sense on self-hosted runner: the intermediate files are preserved between builds and storing/updating them from the network brings no benefits besides increasing the build time. |
problem solved then. :-) |
@nixomose i'm closing the issue because it is solved, but please feel free to reopen it or create a new one in case if the problem appears once again. |
Description:
Post install action can take 20-30 minutes on our self-hosted mac-mini
Action version:
@ 4
Platform:
Runner type:
Tools version:
~1.20.8
Repro steps:
https://github.com/anyproto/anytype-heart/actions/runs/6405381199/job/17387801235
Just build the project
Expected behavior:
Fast post install step
Actual behavior:
Long post install step
The text was updated successfully, but these errors were encountered: