Updating actions/cache@v3 to v4 to run on node20 #14
Description
Activity
@devlsat This action is a shell action and fundamentally does not use node js. However, note that Amazon linux 2 has problems running node 20 because of its dependency with old GLIBC version.
If you are facing issues in running, kindly consider this option
You are right.. this might help..
Looking into why the CI did not get triggered for your PR.
Closing the issue
Reacted by Kishan BReopening this issue to keep track of making this action node version agnostic
@devlsat This Concern of referencing old node version is now fixed with the latest release. If you run trigger a new job you should see it disappear. As a big performance bonus, the python installation time should go from ~1 minute to ~25 seconds .
Give it a spin and let know your feedback :-)
Facing this issue with the latest version
Was working fine with v1.0.8
Reacted by Kishan B@devlsat Interestingly v1.0.8 also has references to the $HOME variable.. Thinking about potential root causes... you have any thoughts?
setup-python-amazon-linux/action.yml
Line 33 in 976096e
@devlsat Have released a possible fix for this in the latest release (v1.0.12).. Can you try running it with either v1.0.12 tag or v1 tag?
Nope
Same error, but got a description this time
Reacted by Kishan B@devlsat If you login to the self hosted runner and run
echo "$HOME"does it fail or succeed?Blank empty output
@devlsat Is this action directly running in the EC2 runner machine or within a Docker container runner?
1 remaining item
I launched an EC2 with amazon linux 2023 AMI and i see
$HOMEis present (screenshot below).What is the output of
whoamicommand? Also is the container being started in a login shell if not this problem might occur
It doesnt
@devlsat Which is the version of this action that is working fine for you?
v1.0.8 works perfectly
Reacted by Kishan B@devlsat Is it correct to assume the new versions of this action are working for you?
@kishaningithub I've tried v1.0.14 and v1.0.15, these didn't work for me, I was getting same error as @devlsat had.
v1.0.8 works ok for me though.@ivanokhotnikov Can you give a screenshot or a text version of the full error you are getting? That will help me debug better
Reacted by Kishan B@ivanokhotnikov Have published a new version v1.0.16 with the fix. Can you give it a spin? You can either use v1 or v1.0.16
same issue, I'm not sure if caching is at play here, but I won't be able to investigate further
Reacted by Kishan BThanks for the screenshot @ivanokhotnikov It was useful! Have released a new version v1.0.17 with the fix. Can you give it a spin? You can either use v1 or v1.0.17
@ivanokhotnikov Did you get a chance to try out the latest version?
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
actions/cache@v3 runs on node16 which is deprecated, requesting to migrate to v4