-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to reuse cached tools on arch armv7 (Raspberry) #793
Comments
Hello @louislam ! Thank you for creating the issue and the PR :) We will investigate them and see what can be done |
Hello @louislam. The pull request was merged. Could you please try to use For now I'm going to reopen the issue because I'd like to close when the new version of setup-node is released. |
@dmitry-shibanov I can confirm it is fixed, it is now looking for Full Log: |
Tested 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/arm
instead 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
armv7l
toarm
,setup-node
will 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.
![](https://private-user-images.githubusercontent.com/1336778/250944124-0ba649dc-53e5-4bcd-a1e8-7c2e1c3b2068.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0MDUyNDMsIm5iZiI6MTcyNDQwNDk0MywicGF0aCI6Ii8xMzM2Nzc4LzI1MDk0NDEyNC0wYmE2NDlkYy01M2U1LTRiY2QtYTFlOC03YzJlMWMzYjIwNjgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjNUMDkyMjIzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YzE1ZjJmMTAyYmU5MGQxOGVjMDc4MzFiODMwZjAxOTE3NDAyM2Y5YWMyYmM3NDYwNzJmNGQ5ZmRhN2U5MzhmZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.tD76Q5TcN-xWvpNzuIyOFN9pYVdfzM-uyu0fcdonL7Y)
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.
The text was updated successfully, but these errors were encountered: