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
Shortly after the migration to Github actions, something changed which broke the automated tests covering the command line.
This may indicate that the build of the command line would also be broken for newer versions of dotnet/msbuild, or that the problem is unique to the tests. I don't have time to investigate what's changed and how to fix it at this time, so I'm stopping deploying new versions of the command line in the hope that the old one will continue to work.
Some manual testing of the command line with latest versions of dotnet would be a good first port of call for understanding this issue.
On a machine where the tests fail (whole solution tests - currently skipped):
Check if the currently released commandline can convert the solution used in the tests
Check if a newly compiled commandline can convert the solution used in the tests
Shortly after the migration to Github actions, something changed which broke the automated tests covering the command line.
This may indicate that the build of the command line would also be broken for newer versions of dotnet/msbuild, or that the problem is unique to the tests. I don't have time to investigate what's changed and how to fix it at this time, so I'm stopping deploying new versions of the command line in the hope that the old one will continue to work.
Some manual testing of the command line with latest versions of dotnet would be a good first port of call for understanding this issue.
On a machine where the tests fail (whole solution tests - currently skipped):
#706 (comment)
The text was updated successfully, but these errors were encountered: