-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Fix python interpreter detection #262
Conversation
LGTM! Have you tested this with your self-hosted runner? uses: sorekz/publish-unit-test-result-action/composite@master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pending test with self-hosted runner.
Yes. However there was one additional step. By default the $PATH contains The best solution would probably be to check for python.exe first on Windows or to always check the Edit: |
I have added the version check to amend |
The check is working however I'm now getting an error when creating the link, which makes me think if I also copied the exe at some point 🤔 because I think that line shouldn't have worked before. Or of course even better when the action is not creating files next to the python.exe because in a company environment where the users eventually have a system python installation but no admin permission they can not write to C:/Programs and that operation will fail. E.g. create the file in (a subfolder of) $RUNNER_TEMP and add that to the path. The $RUNNER_TEMP is cleaned up after each job. |
Very good points, I have fixed the symbolic link and now create it in Can you test the composite action from your repo? |
Made some adjustments and used $GITHUB_PATH which prepends the bin/ folder to the PATH. |
Yes, |
|
You are right, reverted that. |
Works 😃 |
Thanks for testing this through! |
This has been released, thanks! |
Currently the composite action does not work on self-hosted Windows runners because the version check does not pass.
The version string is printed with an upper case P, at least for python 3.9. Not sure about older versions so I adjusted the check to work with both.