dotnet test - The argument /noconsolelogger is invalid. about teamcity-dotnet-plugin HOT 11 CLOSED

The new issue is different from the one described in this ticket. We have other ticket for the issue related to SDK 6.0.300: https://youtrack.jetbrains.com/issue/TW-76189

from teamcity-dotnet-plugin.

Hey there -

We just upgraded to .NET 6.0 - we're seeing the similar following error.

Step 4/11: Running Unit Tests (.NET)
  dotnet test
    Starting: .NET SDK 6.0.300 "C:\Program Files\dotnet\dotnet.exe" test C:\BuildAgent\work\54ed349e18c2d874\UnitTests\UnitTests.csproj --settings C:\BuildAgent\work\54ed349e18c2d874\testSettings.runsettings @C:\BuildAgent\temp\agentTmp\2.rsp
    in directory: C:\BuildAgent\work\54ed349e18c2d874
    Microsoft (R) Test Execution Command Line Tool Version 17.2.0 (x64)
    Copyright (c) Microsoft Corporation.  All rights reserved.
    
    The argument /noconsolelogger is invalid. Please use the /help option to check the list of valid arguments.
    Process exited with code 1
    Process exited with code 1 (Step: Running Unit Tests (.NET))
  Step Running Unit Tests (.NET) failed
  Error message: Step Running Unit Tests (.NET) failed

I'm on
TeamCity Professional 2022.04 (build 108502)

Going into C:\BuildAgent\work\54ed349e18c2d874 and manually running "C:\Program Files\dotnet\dotnet.exe" test C:\BuildAgent\work\54ed349e18c2d874\UnitTests\UnitTests.csproj --settings C:\BuildAgent\work\54ed349e18c2d874\testSettings.runsettings works as expected.

The problem appears to be that the first line of C:\BuildAgent\temp\agentTmp\2.rsp is \noconsolelogger , which is invalid syntax for dotnet test afaik.

from teamcity-dotnet-plugin.

The related issue: https://youtrack.jetbrains.com/issue/TW-64569

from teamcity-dotnet-plugin.

@NikolayPianikov thx. works now

awesome work!

from teamcity-dotnet-plugin.

The output for me of manually typing:

λ  "C:\Program Files\dotnet\dotnet.exe" test C:\BuildAgent\work\54ed349e18c2d874\UnitTests\UnitTests.csproj --settings C:\BuildAgent\work\54ed349e18c2d874\testSettings.runsettings
  Determining projects to restore...
  All projects are up-to-date for restore.
  [... snip ...]
Test run for C:\BuildAgent\work\54ed349e18c2d874\UnitTests\bin\Debug\net6.0\UnitTests.dll (.NETCoreApp,Version=v6.0)
Microsoft (R) Test Execution Command Line Tool Version 17.2.0 (x64)
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.

Passed!  - Failed:     0, Passed:   255, Skipped:     0, Total:   255, Duration: 14 s - UnitTests.dll (net6.0)```

from teamcity-dotnet-plugin.

We are having the same issue with a temp file called 11.rsp. The first line in this file is /noconsolelogger. This is causing builds to fail with strange errors. The error appears to be related to the line directly after /noconsolelogger being injected into the dotnet test command without a preceding space.

So if before it would have been dotnet test proj.csproj /noconsolelogger <line2>, it looks like it's now dotnet test proj.csproj<line2> or something similar. It's hard to tell.

from teamcity-dotnet-plugin.

@schrufygroovy try using the command vstest instead as workaround

from teamcity-dotnet-plugin.

We should support a testing assembly as target for dotnet test command since 3.1.100

from teamcity-dotnet-plugin.

@schrufygroovy, which version of TeamCity do you have installed?

from teamcity-dotnet-plugin.

@schrufygroovy, which version of TeamCity do you have installed?

TeamCity Professional 2019.2.1 (build 71758)
I ensured I am using the latest version before I submitted the report.

from teamcity-dotnet-plugin.

@schrufygroovy It's brilliant and you could try the latest plugin

from teamcity-dotnet-plugin.