Stream: git-wasmtime

Topic: wasmtime / issue #6285 Caches are not working on GitHub A...

Wasmtime GitHub notifications bot (Apr 25 2023 at 18:21):

alexcrichton opened issue #6285:

One thing I forgot about when enabling the Merge Queue feature for this repository is that the existing usages of actions/cache are all broken now. The problem appears to be that caches are associated with a branch and while caches can pull from the "base branch" the base branch in our case is main which never runs CI. This means that all branches are always separate and have no shared base to pull from.

I posted about this here on the github merge queue discussion feedback but wanted to open up something here to track this. I was about to make a PR to remove all the caches but that didn't feel quite right, so I went this route instead.

Wasmtime GitHub notifications bot (Apr 25 2023 at 20:21):

tschneidereit commented on issue #6285:

Could we do a daily cron-triggered CI run on main to prime the caches?

Wasmtime GitHub notifications bot (Apr 26 2023 at 14:14):

alexcrichton commented on issue #6285:

Oh yes indeed, that's a great idea!

Wasmtime GitHub notifications bot (Apr 26 2023 at 16:34):

pchickey closed issue #6285:

One thing I forgot about when enabling the Merge Queue feature for this repository is that the existing usages of actions/cache are all broken now. The problem appears to be that caches are associated with a branch and while caches can pull from the "base branch" the base branch in our case is main which never runs CI. This means that all branches are always separate and have no shared base to pull from.

I posted about this here on the github merge queue discussion feedback but wanted to open up something here to track this. I was about to make a PR to remove all the caches but that didn't feel quite right, so I went this route instead.

Last updated: Nov 22 2024 at 16:03 UTC