Skip to content
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.

Sign up for GitHub

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

Jump to bottom

invalidate-cache: true doesn't work on self-hosted runners #73

Open
cap10morgan opened this issue Aug 29, 2022 · 0 comments · May be fixed by #74
Open

invalidate-cache: true doesn't work on self-hosted runners #73

cap10morgan opened this issue Aug 29, 2022 · 0 comments · May be fixed by #74

Comments

@cap10morgan
Copy link
Contributor

Self-hosted runners persist a lot more across runs vs. GitHub-provided runners. Currently the code just skips cache restoration to the runner's local FS when invalidate-cache: true is set. However, the cache is usually already present in its restored location on self-hosted runners. So an additional check is needed to ignore that w/ invalidate-cache: true. I'll work up a PR.
@cap10morgan cap10morgan linked a pull request Aug 29, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ignore cache if invalidate-cache: true fluree/setup-clojure
1 participant
@cap10morgan