I’m relying on the prefix-matching and “most recent” behaviour described here to obtain the cache from the latest build for the current branch. However, Circle sometimes seems to be picking up random older versions. For example, for my latest two builds on the develop branch: Build #2227 Found a…

I’m seeing this as well. Started happening a few days ago: Six days ago, build 45083 was pulling a cache from build 45062, the previous build on the same branch. The next build on the same branch (45129, from two days ago) is now pulling a cache from build 44730–a build from 15 days ago.

[Edit] Nevermind, I spoke too soon. Some builds are restoring the proper cache, but others are still restoring from 44730 (consistently)

Yup, I’m still seeing this too.

Why no response yet from circle ci? Today this resulted in deploy of month old version of code without any notice not mentioning all the additional time spend building as the cache is not working properly. This is urgent for us, otherwise we will need to find other service for build and deployment.

We’ve had a couple support tickets come in about this and our engineers are currently investigating it. It took our support team some time to rule out that these issues weren’t due to restore cache key ordering or substring matches. In one case, a user had a config race condition. His workflow re…

Thanks for the response Eric Do you have any recommendation of what can be used as mechanism to move built docker image from one job to another? As I said we have one job that builds the image and second that deploys it, tied into one workflow. We use cache so we do not have to rebuild the image ag…

Our engineers have pushed out a fix for this. Can you all run some more jobs on the problematic projects/workflows and post back here if you’re still seeing old caches being used? [image] aocenas: Do you have any recommendation of what can be used as mechanism to move built docker image from …

Hi @Eric , thanks for the update/fix! Anecdotally my last seven builds have all done the correct thing in terms of caching, so it looks promising. I’ll keep an eye on things for the next day or so.

It looks like after the fix was pushed, my restore_cache steps failed with: Skipping cache - error checking storage: RequestError: send request failed caused by: Get https://circle-production-customer-artifacts.s3.amazonaws.com/...snip...: x509: failed to load system roots and no roots provided I …

Non-deterministic cache-restore behaviour

Feedback & Bug Reports

jaredledvina September 12, 2017, 11:38pm 5

I just commented on Spurious build success as well but, it seems like the Restore Cache step is super wonky as of late. Happy to test config changes to debug the issue if anyone has a suggestion.

Topic		Replies	Views
CIrcleCi failed to restore cache Caching Dependencies	6	2705	August 23, 2023
Getting failed build due to "Github or AWS" circle error every 1 out of 2 builds Feedback & Bug Reports caching	8	2370	November 16, 2015
CircleCI cache issue in Sep 4 outage Feedback & Bug Reports	4	907	September 5, 2018
Cache immutability, and using the cache from the last build Caching Dependencies	3	4660	January 7, 2020
Cache restore step fails Feedback & Bug Reports cache	2	1966	April 5, 2019

Non-deterministic cache-restore behaviour

Related topics