Fresher cache placement issue #54 closed: completed andymccall opened this 21 days ago · 0 comments

Follow-up to issue #28/#51: when both runners hold a job's build cache, prefer the one whose copy is newer. Claims report when each slot last kept a disk (cache_times, Unix ms); the hub ranks a fresher copy (by at least a minute) above an older one, after holding the cache at all and before the image and speed. The placed reason says how old the copy is.