-
Notifications
You must be signed in to change notification settings - Fork 13
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.
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
Q: When to use job-id argument? (reserveCache failed: Cache already exists.) #40
Comments
I'm seeing the same issue here and I'm clueless how to solve it:
Any help is appreciated. Is there an explicit way to invalidate the cache? |
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Dec 4, 2021
This suffer from [1]. [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Dec 5, 2021
This job suffers from [1]. [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Dec 5, 2021
This job suffers from [1]. [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Feb 9, 2022
Try whether the caching issue from [1] has "disappeared". [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Feb 9, 2022
Try whether the caching issue from [1] has "disappeared". [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Feb 28, 2022
This is a try to solve the issue described in [1]. [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Feb 28, 2022
This is a try to solve the issue described in [1]. [1]: burrunan/gradle-cache-action#40 Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, thanks for creating the Action, I really appreciate all the hard work you put into it 🙏 The cache is really efficient and it covers most of the cases with the default settings, nice 👍
I've read the documentaiton and I'm not sure I properly understood how to use your action in a workflow with multiple parallel jobs.
Basically what I'm currently seeing is: "reserveCache failed: Cache already exists."
sample run
full workflow
so I assume I use the action in a wrong way. I wanted to ask about the
job-id
argument, when should one want to provide custom value?According to the documentation it should be used "in in case you want to split caches" - does that create completely separate cache so 2 jobs with different
job-id
s won't share anything? Or is that for optimization purposes and there will be a common part, so basically I should use it whenever something happens in parallel? How do I know if should use it?The text was updated successfully, but these errors were encountered: