Renovate repeatedly fails to update go.sum for some projects because go get ... fails. Possible caching bug?
#32284
Answered
by
rarkins
robbie-demuth
asked this question in
Request Help
-
How are you running Renovate?Self-hosted Renovate If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.GitLab Enterprise Edition v17.4.2-ee (self-hosted) / Renovate 38.130.2 Please tell us more about your question or problemBackgroundBefore diving into the problem, I'd first like to provide a bit more background on how our organization runs Renovate. We self-host GitLab and run Renovate from a central project once an hour via a scheduled pipeline. We use Renovate:
variables:
RENOVATE_BASE_DIR: $CI_PROJECT_DIR/renovate
parallel:
matrix:
- RENOVATE_AUTODISCOVER_FILTER:
- appian/dev/a*
- appian/dev/b*
...
- appian/dev/y*
- appian/dev/z*
cache:
key: ${RENOVATE_AUTODISCOVER_FILTER}-renovate
paths:
- $RENOVATE_BASE_DIR/cacheProblemOur team owns multiple Go projects and frequently runs into problems with Renovate updating
StoryTo detail the problem, I'd like to recount the story of how Renovate handled the dependency update of the same dependency for 3 of our projects. The projects were:
The dependency update was Part 1: Renovate ran for the first time after
|
Beta Was this translation helpful? Give feedback.
Answered by
rarkins
Nov 1, 2024
Replies: 1 comment 8 replies
-
|
Isn't the question "why is go get failing?" Renovate is calling go. You can see the command in the logs. Similarly it would be a go cache, not a renovate cache (it's data saved and loaded by go and not renovate data) |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
How does Renovate cache Go's module cache? Does each project (or branch, etc) have its own module cache? How do you explain |
Beta Was this translation helpful? Give feedback.
-
|
Renovate doesn't do anything special with go's cache. The cache goes to the same place for every repo. Unlike gitlab CI, renovate doesn't compress, copy or restore it ever either. |
Beta Was this translation helpful? Give feedback.
Answer selected by
robbie-demuth
-
|
Most likely explanation is that you have multiple processes writing to the same cache and corrupting it somehow. Or does each of your 26 processes keep their own cache? |
Beta Was this translation helpful? Give feedback.
-
|
This is interesting. I see the following for {"name":"renovate","hostname":"runner-buz-ttsc-project-1643-concurrent-15-bofvcr5p","pid":81,"level":20,"logContext":"FBPemPhbBHdZEXH1ahEYy","repository":"appian/dev/site-key-handler","msg":"RepoCacheBase.load() - expecting data of type 'string' received 'object' instead - skipping","time":"2024-11-01T00:16:00.995Z","v":0}But the following for {"name":"renovate","hostname":"runner-vvgstsxg-project-1643-concurrent-8-662jq6za","pid":75,"level":20,"logContext":"HzRjL52hKK9eKEus04BtY","repository":"appian/dev/site-data-coordinator","msg":"Repository cache is restored from revision 13","time":"2024-10-31T23:19:49.730Z","v":0} |
Beta Was this translation helpful? Give feedback.
-
Each of the 26 jobs has its own cache. Renovate:
variables:
RENOVATE_BASE_DIR: $CI_PROJECT_DIR/renovate
parallel:
matrix:
- RENOVATE_AUTODISCOVER_FILTER:
- appian/dev/a*
- appian/dev/b*
...
- appian/dev/y*
- appian/dev/z*
cache:
# This ensures each of the 26 jobs has its own cache
key: ${RENOVATE_AUTODISCOVER_FILTER}-renovate
paths:
- $RENOVATE_BASE_DIR/cache |
Beta Was this translation helpful? Give feedback.
-
|
The logs you see are renovate's own cache and should not have any influence on go's cache. Renovate cache should be shared between instances or not used at all. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Renovate doesn't do anything special with go's cache. The cache goes to the same place for every repo. Unlike gitlab CI, renovate doesn't compress, copy or restore it ever either.