- name: Attempt Cache Restore with Full Debug uses: actions/cache@v4 with: path: node_modules key: debug-$ runner.os -$ steps.sim.outputs.hash restore-keys: debug-$ runner.os -
run. If you need to debug a specific failure, download the Artifact, not the Cache. State Consistency:
The debug-action-cache philosophy is evolving into . Instead of raw [debug] lines, you will soon see JSON logs you can pipe into jq .
Compare two logs using a diff tool. Look for absolute paths that should be relative, or environment variables like PATH or PWD that differ between developer machines. 2. Analyzing the "Action Key"
- name: Inspect cache contents run: | echo "Listing cached Python site-packages" ls -la venv/lib/python3.9/site-packages/ | head -20 echo "Checking for stale binaries" find venv -name "*.so" -exec ls -lh {} \;
- name: Attempt Cache Restore with Full Debug uses: actions/cache@v4 with: path: node_modules key: debug-$ runner.os -$ steps.sim.outputs.hash restore-keys: debug-$ runner.os -
run. If you need to debug a specific failure, download the Artifact, not the Cache. State Consistency:
The debug-action-cache philosophy is evolving into . Instead of raw [debug] lines, you will soon see JSON logs you can pipe into jq .
Compare two logs using a diff tool. Look for absolute paths that should be relative, or environment variables like PATH or PWD that differ between developer machines. 2. Analyzing the "Action Key"
- name: Inspect cache contents run: | echo "Listing cached Python site-packages" ls -la venv/lib/python3.9/site-packages/ | head -20 echo "Checking for stale binaries" find venv -name "*.so" -exec ls -lh {} \;
