cyclane/kovalhome
1
1
Fork 0
Code Issues 7 Pull Requests 1 Actions Packages Projects 3 Releases Activity

Gitea: act_runner is wonky and slow #17

New Issue
Closed
opened 2023-12-02 21:38:06 +00:00 by cyclane · 3 comments
cyclane commented 2023-12-02 21:38:06 +00:00
Owner
Copy Link
- [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).
cyclane added the
Kind/Bug
Priority
Medium
 labels 2023-12-02 21:38:06 +00:00
cyclane added this to the Services project 2023-12-02 21:38:06 +00:00
cyclane added
Priority
Critical
 and removed
Priority
Medium
 labels 2023-12-30 17:25:36 +00:00
cyclane commented 2023-12-30 17:27:35 +00:00
Author
Owner
Copy Link

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.
cyclane commented 2023-12-31 07:04:49 +00:00
Author
Owner
Copy Link

Cache issue should be fixed with this: https://docs.gitea.com/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image

Cache issue should be fixed with this: https://docs.gitea.com/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image
cyclane commented 2023-12-31 07:11:01 +00:00
Author
Owner
Copy Link

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.

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Spike
Research issues and pull requests
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Bug
Priority
Critical
Milestone
No items
No Milestone
Projects
Clear projects
No project Services
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cyclane/kovalhome#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?