-
-
Notifications
You must be signed in to change notification settings - Fork 184
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 use Action on Self-Hosted Windows Runner with powershell
shell
#634
Comments
Looks like you do not have PowerShell ( |
Thannks for your reply @EnricoMi , I have Powershell installed already in my machine and same is updated at environment variables also. |
Looks like PowerShell v5 provides powershell.exe whereas PowerShell v6 and v7 provide pwsh.exe. |
Can you test the following please:
|
This action is tag is not allowed as of now in my enterprise organization. but let me download the action manually and test once please. |
@EnricoMi , I dont find any action/sub folder for powershell under windows folder in the code. Can i still use the action as you mentioned? uses: EnricoMi/publish-unit-test-result-action/windows/powershell@windows-powershell |
Check out branch |
Looks like |
powershell
shell
Thank you @EnricoMi, I have upgraded my powershell to v7 and now i can able to use the action and it seems working fine with v7. But few of the file formats are accepting it seems. Is OpenCover.xml & Cobertura.xml are accepted formats in this action? |
Sounds like those file contain test coverage information, which are not test result information. |
yes @EnricoMi , we have coverage information in it. do you have any plan to create an action to support coverage as well please? |
Adding coverage sounds like a natural fit for this action. But I have not looked into this. Happy to review pull requests on this area. |
We are trying using the Windows version of action to publish unit tests, but we are getting below error as mentioned in the screen shot.
Below is the task which we have added in the yml file.
The text was updated successfully, but these errors were encountered: