cerc-io/hosting
17
0
Fork 0
Code Issues 7 Pull Requests 2 Packages Projects Releases Wiki Activity

Set address for runner cache #57

Merged
telackey merged 1 commits from runner-cache into main 2023-10-04 17:26:10 +00:00
Conversation 4 Commits 1 Files Changed 2 +4 -2
roysc commented 2023-09-20 06:12:00 +00:00
Member
Copy Link

I've seen some issues with actions timing out when fetching from the cache (e.g. setup-go step here) - this has fixed it locally for me.

I've seen some issues with actions timing out when fetching from the cache (e.g. setup-go step [here](https://git.vdb.to/cerc-io/ipld-eth-statedb/actions/runs/1/jobs/0)) - this has fixed it locally for me.
telackey commented 2023-09-22 17:51:15 +00:00
Member
Copy Link

I think I need a bit more context, as I have to admit I don't understand either the problem or how the changes fix it.

I think I need a bit more context, as I have to admit I don't understand either the problem or how the changes fix it.
roysc commented 2023-09-24 07:08:08 +00:00
Author
Member
Copy Link

Well setup-go is timing out when trying to access the cache:
::warning::Failed to restore: getCacheEntry failed: connect ETIMEDOUT 172.17.0.3:36843
So the step succeeds, but takes 5 minutes. It turns out this is expected when the job containers can't find the runner cache: https://docs.gitea.com/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image
The comment in the file says it should be detected, but apparently, not so much.

The change in the gitea script is unrelated. I can split it out.

Well setup-go is timing out when trying to access the cache: `::warning::Failed to restore: getCacheEntry failed: connect ETIMEDOUT 172.17.0.3:36843` So the step succeeds, but takes 5 minutes. It turns out this is expected when the job containers can't find the runner cache: https://docs.gitea.com/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image The comment in the file says it should be detected, but apparently, not so much. The change in the gitea script is unrelated. I can split it out.
telackey approved these changes 2023-09-25 17:28:56 +00:00
roysc commented 2023-10-04 07:48:33 +00:00
Author
Member
Copy Link

I don't have write access, could someone merge this?

I don't have write access, could someone merge this?
dboreham commented 2023-10-04 17:03:56 +00:00
Owner
Copy Link

I don't have write access, could someone merge this?

Added you to the repo.

> I don't have write access, could someone merge this? Added you to the repo.
Sign in to join this conversation.
Reviewers
No reviewers
telackey
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
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/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

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
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
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/hosting#57
No description provided.
Delete Branch "runner-cache"

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?