cache doesn't seem to work, and might be the cause of the above (but should be fixed nevertheless).
- [x] act_runner will some times take ages on "Complete Job" - https://git.koval.net/cyclane/teamcity-gitea-test-task/actions/runs/20/jobs/0
- Now it just fails https://git.koval.net/cyclane/teamcity-executors-test-task/actions/runs/15/jobs/0 .
- [x] cache doesn't seem to work, and might be the cause of the above (but should be fixed nevertheless).
Raising priority to Critical - this is affecting all CI on the gitea instance now.
#19 is also a Gitea issue, is it possible this instance is somehow corrupted?
Nevertheless, all issues still seem to be linked to cache timing out. I think this can all be fixed by finding and removing the cause of that.
Raising priority to `Critical` - this is affecting all CI on the gitea instance now.
#19 is also a Gitea issue, is it possible this instance is somehow corrupted?
Nevertheless, all issues still seem to be linked to cache timing out. I think this can all be fixed by finding and removing the cause of that.
This should vastly improve performance of most of the CI in existing projects too, since many 3rd-party actions use cache as well.
See https://git.koval.net/cyclane/actions-cache-testing/actions/runs/1/jobs/0 , cache has been fixed. "Complete Job" was taking ages similarly due to cache issues (trying to save cache at the end) I believe this is all done now (finally).
This should vastly improve performance of most of the CI in existing projects too, since many 3rd-party actions use cache as well.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Raising priority to
Critical- this is affecting all CI on the gitea instance now.#19 is also a Gitea issue, is it possible this instance is somehow corrupted?
Nevertheless, all issues still seem to be linked to cache timing out. I think this can all be fixed by finding and removing the cause of that.
Cache issue should be fixed with this: https://docs.gitea.com/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image
See https://git.koval.net/cyclane/actions-cache-testing/actions/runs/1/jobs/0 , cache has been fixed. "Complete Job" was taking ages similarly due to cache issues (trying to save cache at the end) I believe this is all done now (finally).
This should vastly improve performance of most of the CI in existing projects too, since many 3rd-party actions use cache as well.