-
Notifications
You must be signed in to change notification settings - Fork 504
Sometimes got error "Unable to locate dotnet CLI. Ensure that it is on the PATH" #564
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
Comments
Hello @hongbo-miao, |
Just found more people having same issue. |
Hello @hongbo-miao, We have reviewed your comment and would like to clarify that the DOTNET_ROOT environment variable now points to D:\a_temp.dotnet instead of C:\Program Files\dotnet because the DOTNET_INSTALL_DIR environment variable is set to ${{ runner.temp }}/.dotnet. The setup-dotnet action sets DOTNET_ROOT to the same value as DOTNET_INSTALL_DIR. |
Hello @hongbo-miao, please let us know if you have any concerns or need further clarification on the above to assist further :) |
@aparnajyothi-y there is only has a workaround way, and still not fixed. |
Description:
I found
setup-dotnet
is not always reliable.For example, in same GitHub Action build:
Attempt #1
failed: https://github.com/hongbo-miao/hongbomiao.com/actions/runs/12211957209/attempts/1Attempt #2
succeed: https://github.com/hongbo-miao/hongbomiao.com/actions/runs/12211957209Platform:
Runner type:
Repro steps:
hardware-in-the-loop/national-instruments/veristand/VeriStandZeroMQBridge/global.json
Expected behavior:
I expect dotnet CLI work all time if no code changes.
Actual behavior:
Even same code in same build, sometimes I got error "Unable to locate dotnet CLI. Ensure that it is on the PATH"
Also, for this pull request, when bumping csharpier from 0.30.2 to 0.30.3, no matter how many times I tried, I always got
Build log
You can see dotnet CLI got installed at
C:\Program Files\dotnet
, but next step it says cannot find itThe text was updated successfully, but these errors were encountered: