Closed anthonyc4 closed 11 months ago
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days.
This issue was closed because it has been inactive for 5 days since being marked as stale.
We have noticed a problem that if we used workflow_dispatch that, not always, the cache would return a hit with 0mb of content. Since we are using this to cache node_modules, it means the rest of the workflow will not work. We are using GIthub Enterprise which apparently does not have the same API to be able to burst a cache element.
Our jobs are running on pull_request and can be dispatched by the user. Running via pull_request does seem to work
Here is a log:
While doing some debugging, when the cache was 0mb, we saw the output looked like this:
In this case, the package-lock is correct, but for some reason, the node_modules are not retrieved from cache. Again, this only was happening on
workflow_dispatch
We were able to create a work around that runs right after the
actions/cache
that looks like this (but it is a hack). This will run thenpm ci
if the cache size is less than 1mb.