TestWillNotBuildTheProjectIfNoBuildArgsIsGiven is failing CLI update stage 0
See original GitHub issueWhen updating to the latest stage 0, TestWillNotBuildTheProjectIfNoBuildArgsIsGiven fails. This test is maintained by VSTest. It only fails in Linux.
Expected string \"The argument /Users/vsts/agent/2.155.1/work/1/s/artifacts/tmp/Release/test/dotnet-test.Tests/5/VSTestCore/bin/Release/netcoreapp3.0/VSTestCore.dll is invalid. Please use the /help option to check the list of valid arguments.\" to contain \"The test source file \\\"/Users/vsts/agent/2.155.1/work/1/s/artifacts/tmp/Release/test/dotnet-test.Tests/5/VSTestCore/bin/Release/netcoreapp3.0/VSTestCore.dll\\\" provided was not found.\".
However, once you fix the issue in vstest. We need an insertion to toolset. And we need to wait for toolset->core-sdk->CLI to unblock. I am wondering if you could move this test to vstest repo. I don’t think SDK is required to test argument validation.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
update-stage — AWS CLI 1.29.30 Command Reference
The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@wli3 I was able to reproduce the issue and pass test in Linux. After dotnet
3.0.100-preview 8
there was a change in TestPlatform, which added new exception message, when user send incorrect arguments in console. You need to change your error message in your test to pass the build. Please look at this draft PR, which I created to reproduce the issue : https://github.com/dotnet/cli/pull/13401Thanks a lot @Sanan07 !
I’ve added
--diag
and it does show something that may be related, but I’m not sure it makes sense, at least not to me. It says something about the path being absolute, albeit I’m not sure this is an error(?). Here is the output:And here is the output of
dotnet --info
: