Repository navigation
Unable to reuse cached tools on arch armv7 (Raspberry) #793
Description
Activity
Hello @louislam ! Thank you for creating the issue and the PR :) We will investigate them and see what can be done
Reacted by Louis Lam and Zaid HafeezHello @louislam. The pull request was merged. Could you please try to use
actions/setup-node@mainto confirm that it works as expected?For now I'm going to reopen the issue because I'd like to close when the new version of setup-node is released.
Reacted by Louis Lam@dmitry-shibanov I can confirm it is fixed, it is now looking for
armv7linstead ofarm. Thank you.
Full Log:
https://github.com/louislam/uptime-kuma/actions/runs/5532726517/jobs/10095225803?pr=3354Tested 3.8.0 and double confirmed that it has been fixed.
Description:
On armv7, setup-node will download Node.js from official and extract to
_work/_tool/node/18.16.1/armv7l.However, setup-node is searching for the cache in
_work/_tool/node/18.16.1/arminstead of_work/_tool/node/18.16.1/armv7l. As a result, it can never hit the cache.My current workaround:
Manually rename the directory from
armv7ltoarm,setup-nodewill be able to use cached tool in the next run.Log: https://github.com/louislam/uptime-kuma/actions/runs/5456311185/jobs/9928952991?pr=3354
The image shows that the directory name do not match.
Action version:
4.305.0
Platform:
Runner type:
Tools version:
Repro steps:
Option 1:
In case you don't have such hardware. You can fork this pr and create pr on my repo if you want to test: louislam/uptime-kuma#3354. The job
armv7-simple-test (ARMv7, 16)is always reproducible.Option 2:
Expected behavior:
Node.js could be reuse in the next run.
Actual behavior:
Node.js will be downloaded for every run, the cached tool is never used.