Cache not found for input keys
See original GitHub issueNot sure what I’m missing here:
jobs:
tests:
name: Run all tests
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Setup node 14
uses: actions/setup-node@v1
with:
node-version: 14.x
- name: Get yarn cache directory path
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn cache dir)"
- uses: actions/cache@v2
id: yarn-cache # use this to check for `cache-hit` (`steps.yarn-cache.outputs.cache-hit != 'true'`)yarn cache dir
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ runner.os }}-yarn-
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:11
Top Results From Across the Web
Cache not found because action searches for "<key>, <key ...
As you see in the text, this failure happens on Windows. I am doing the same under Ubuntu, but then there is no...
Read more >Actions/cache: Cache not being hit despite of being present
Cache's are scoped to a key and a branch, so a cache created on branch-A won't be accessible by branch-B unless branch-A is...
Read more >Using Github action cache - Questions / Help - Elixir Forum
I am using github actions to run tests for my Elixir repo. Here is part of my github workflow .yml: steps: - uses:...
Read more >GitHub Action caching - David Gardiner
Here's the cache action that I'm using for my Show Missing extension. - uses: actions/cache@v2 with: path: ${{ github.workspace }}/.nuget/ ...
Read more >actions - Bountysource
Cache not found for input keys : Windows-gradle-... But then in each "Post Cache Gradle dependency cache" step, it says: [warning]Cache already exists ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, most of issuer above is using v2, let me try v3! One of my friends’ new repo that is using v3 is working nicely.
Yes, package-lock file only changes after doing
npm i
. So, this should be the reason. Closing now. Thank you.