Intermittent error "Unable to locate dotnet CLI. Ensure that it is on the PATH."

[christophwille]

This started happening to our Github builds this weekend:

We never had any issues whatsoever, so initially we were looking at the newly installed net90, but then found microsoft/azure-pipelines-tasks#19162 (and by extension #2000). However, when locking to the latest version in https://github.com/icsharpcode/ILSpy/pull/3338/files we still see "Unable to locate dotnet CLI. Ensure that it is on the PATH.".

So it wasn't the old-ish version of dotnet-format that tripped us up but it happens also with the latest 8-series one. Any ideas/pointers where to start looking next? This flakiness is annoying (but not a showstopper atm).

[RikkiGibson]

It might help us diagnose the issue if we add logging to the 'catch' block below

https://github.com/dotnet/sdk/blob/5be682bcb813ce9dadc2f091078f5a0075d9f4a9/src/BuiltInTools/dotnet-format/Commands/FormatCommandCommon.cs#L357

[RamaInfraOps]

This started happening to our Github builds this weekend:

We never had any issues whatsoever, so initially we were looking at the newly installed net90, but then found microsoft/azure-pipelines-tasks#19162 (and by extension #2000). However, when locking to the latest version in https://github.com/icsharpcode/ILSpy/pull/3338/files we still see "Unable to locate dotnet CLI. Ensure that it is on the PATH.".

So it wasn't the old-ish version of dotnet-format that tripped us up but it happens also with the latest 8-series one. Any ideas/pointers where to start looking next? This flakiness is annoying (but not a showstopper atm).

facing the same issue and its quite annoying as it is happening on multiple workflows. Any time line for this fix?