You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me I can't run my github workflow including dotnet format as it silently fails with error message Process completed with exit code 2.
It is working if I pin the dotnet version to 6.0.102here.
I call dotnet format --no-restore --verify-no-changes --exclude *.Generated.cssee here.
I have a PR to update to current dotnet here. It still fails despite it is using the new release see here. The version number can be seen here. There is no entry which states that a file would have been changed by the run which would explain the non 0 exit code.
The format is only verified under linux. The bug occured in parallel to #1519 but is not fixed with the most recent version update. Perhaps there is another bug?
The text was updated successfully, but these errors were encountered:
badcel
changed the title
Verifying no changes still broken
Verifying no changes still broken?
Apr 13, 2022
I got the reason for the failed CI build. dotnet format outputs warnings which result in the non 0 exit code for version 6.0.202. For 6.0.102 the same warnings did not result in a non 0 exit code. If this is intended behaviour this issue can be closed.
For me I can't run my github workflow including
dotnet format
as it silently fails with error messageProcess completed with exit code 2.
It is working if I pin the dotnet version to
6.0.102
here.I call
dotnet format --no-restore --verify-no-changes --exclude *.Generated.cs
see here.I have a PR to update to current dotnet here. It still fails despite it is using the new release see here. The version number can be seen here. There is no entry which states that a file would have been changed by the run which would explain the non 0 exit code.
The format is only verified under linux. The bug occured in parallel to #1519 but is not fixed with the most recent version update. Perhaps there is another bug?
The text was updated successfully, but these errors were encountered: