Closed fat-fellow closed 1 year ago
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:
- name: Install Go
uses: actions/setup-go@v4
with:
go-version: "~1.20.8"
cache: false
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. If you do the exact same thing on a self hosted windows machine, it takes 30+ minutes to do the same tar. disabling the cache makes that not happen, and the cleanup step takes no time at all, so I lose out on caching, but at least I don't have to wait a half hour for my ci workflow to complete.
@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. :-) it is odd that it takes sooooooooooooooo much longer to tar up on windows though.
@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