guessing new backend is case-sensitive in base image name?

[aryairani]

an actions/cache/restore action started failing for me during the brownout. the only explanation I could guess was that actions/cache/save was running on macOS-13 whereas actions/cache/restore was running on macos-13. I didn't see this change documented anywhere in the migration guide; but also it seems easy enough to make the backend case-insensitive. Not sure if there's any reason not to do that? Or make runs-on case-sensitive.

https://github.com/unisonweb/unison/actions/runs/13251002645/job/37026161441

[aryairani]

I've been having similar failures recently even without a case difference in the base image name; so maybe this is a red herring, or I can open a separate ticket for those?

https://github.com/unisonweb/unison/actions/runs/13184837131/job/37172496896

Is the new cache backend running right now and is it just less reliable? more ways to get a cache miss?

[aryairani]

I'm guessing the second issue is #1547, and the initial issue may have been too.

[JoannaaKL]

Hi @aryairani, thank you for raising this issue. It is a bug and we are working on a fix.