Debug-action-cache [new]
To debug a GitHub Actions cache and inspect its solid content, you can use several methods ranging from built-in debug modes to external CLI tools. 1. Enable Action Debug Logging
2. Use the actions/cache Debug Output
If using actions/cache@v3, add the verbose input: debug-action-cache
Best Practices for Implementing Debug Action Cache To debug a GitHub Actions cache and inspect
- Cache Store: A data structure that stores the results of debug actions.
- Cache Key: A unique identifier for each debug action, used to retrieve the cached result.
- Cache Hit: When a debug action is performed, the cache is checked for a matching cache key. If a match is found, the cached result is returned.
- Cache Miss: If no matching cache key is found, the debug action is performed, and the result is stored in the cache.
# On the self-hosted machine
sudo find / -name "node_modules" -path "*/actions-runner/_work/*" -type d
You usually start looking into debug-action-cache for two reasons: Cache Store : A data structure that stores
2. Debugging paths Input
A common mistake is mis-specifying the path. The debug log will show exactly what is being archived:
When using GitHub Actions, debugging the cache often involves setting:ACTIONS_STEP_DEBUG: true