Clean cache after smoke test

[KobayashiAzusa]

Description

Remove /tmp/node-compile-cache after smoke tests

Motivation and Context

The Node.js image, during the build process in the RUN layer, executed Node.js and generated the /tmp/node-compile-cache directory without deleting it. According to subsequent build steps, this directory was deleted in the next RUN, therefore it doesn't exist in the final image (though it's only marked as deleted in the current RUN layer - the original files still reside in the historical layers).

Testing Details

Example Output(if appropriate)

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (3)

• Dockerfile-alpine.template: Language not supported
• Dockerfile-debian.template: Language not supported
• Dockerfile-slim.template: Language not supported

[PeterDaveHello]

I thought the cleanup was only for yarn? I tested node --version & npm --version locally, and also inserted one additional line into the Dockerfile to build the image as below:

&& echo "run \`ls -al /tmp/\`" 1>&2 && ls -al /tmp/ 1>&2 && echo 1>&2 \

None of the results look like we need this cleanup for node and npm smoke tests,

[KobayashiAzusa]

I am not sure which one generated the cache, but it does exist in /tmp after smoke test in layer. This is also reported in #2199.

The patch removed /tmp/* , and cache files disappear.

[PeterDaveHello]

@KobayashiAzusa you are right, I verified your thought, and I somehow inserted the test command at the wrong place, this is a good catch, thanks!

[PeterDaveHello]

Fun fact: there's no such issue with v18, v20, or even v21, but v22 and v23. That's why I couldn't reproduce the issue the first time. #2199 was very helpful in helping me notice that difference!

[PeterDaveHello]

This won't hurt those versions that are not affected anyway.