Self-hosted macOS runner cache timeout

[Akhrorkhuja]

Experiencing issue with cache which takes !1.68 GB space. Is it related with space or something else.

Tried to clear cache, after a few pipelines same issue.

[Mark C]

Hi @Akhrorkhuja

Welcome to the community.

After clearing the cache, does it work for a few builds then fails on 4th or 5th build?

Regards,
Mark C

[Akhrorkhuja]

Hi Mark.

We're using one device for 2 runners. I think it's the cause of problem. After disabling 2nd runner it works perfectly.

[Shalini R]

It could be related to disk space, but the cache size alone doesn’t necessarily mean that’s the root cause. On a self-hosted macOS runner, I’d also check the runner’s available disk space, cache directory permissions, and whether old cache entries are actually being removed after cleanup.

Since the issue returns after a few pipelines, it may be worth checking whether the pipelines are continuously generating new cache data or whether the cache cleanup process is failing. Looking at the runner logs around the cache restore/save step should help identify where the timeout is occurring.

[Akhrorkhuja]

Disk space is ok. We're running parallel pipelines. May be it's the source of issue. And cache is shared.