Updating actions/cache@v3 to v4 to run on node20

[devlsat]

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

[kishaningithub]

@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

setup-python-amazon-linux/.github/workflows/test.yml

Line 10 in 976096e

ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true

[devlsat]

Okay thanks for the update
So, doing #15 this won't help?
Since

[kishaningithub]

You are right.. this might help..

Looking into why the CI did not get triggered for your PR.

[devlsat]

Closing the issue

[kishaningithub]

Reopening this issue to keep track of making this action node version agnostic

[kishaningithub]

@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 :-)

[devlsat]

Facing this issue with the latest version

Was working fine with v1.0.8

[kishaningithub]

@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

echo "installation_directory=${HOME}/.setup-python-amazon-linux/.python-versions/${exact_python_version}" >> $GITHUB_OUTPUT

[kishaningithub]

@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?

[devlsat]

Nope
Same error, but got a description this time

[kishaningithub]

@devlsat If you login to the self hosted runner and run echo "$HOME" does it fail or succeed?

[devlsat]

Blank empty output

[kishaningithub]

@devlsat Is this action directly running in the EC2 runner machine or within a Docker container runner?

[devlsat]

Docker container runner

[kishaningithub]

I launched an EC2 with amazon linux 2023 AMI and i see $HOME is present (screenshot below).

What is the output of whoami command? Also is the container being started in a login shell if not this problem might occur

[kishaningithub]

@devlsat I have released a possible fix for this in the latest v1.0.13 version viz to force a login shell for bash execution. Can you try upgrading to v1.0.13 or trigger a new run with v1 version?

[devlsat]

It doesnt

[kishaningithub]

@devlsat Which is the version of this action that is working fine for you?

[devlsat]

v1.0.8 works perfectly

[kishaningithub]

@devlsat Have released a new version v1.0.14 which i think should fix the above issue. Kindly check and let me know.

[kishaningithub]

@devlsat Is it correct to assume the new versions of this action are working for you?