Repro steps:
-
Install VS2015 Update 3
-
Install https://dotnet.myget.org/F/roslyn/vsix/eb2680f2-4e63-44a8-adf6-2e667d9f689c-2.0.0.6110410.vsix
-
Install CodeRush for Roslyn v16.2.4
-
Checkout Roslyn post-dev15 branch as of commit https://github.com/dotnet/roslyn/commit/34ca032786199e9fc206037bc6fb5c279cb1eb0b
-
Run the build instructions:
Restore.cmd
msbuild /v:m /m Roslyn.sln -
Try and run any of the tests, e.g., in roslyn\src\Compilers\CSharp\Test\Emit\CodeGen\PropertyTests.cs
Expected behavior: the test is executed
Actual behavior: "Test started…" is shown, after a long wait a lot of errors (see attachment) is shown. Enabling assembly bind failure logging doesn't show any errors at all even after waiting for an hour or so.
Hi Alexei,
Thank you for letting us know about this problem.
I have tried to reproduce it locally but failed. Here is a screencast of my steps: https://www.screencast.com/t/9vXwjRsbyuKr
To help us to determine the cause of this problem, could you provide us with the following information:
Clarify if tests are running in Visual Studio built-in test runner. Open the Test Explorer window via the "Tests | Windows | Test Explorer" menu. Paste the following text "Microsoft.CodeAnalysis.CSharp.UnitTests.CodeGen.PropertyTests" in the filter field atop of this window. The "ExpressionBodedProperty" test should be filtered. Right click on this test and select the "Run Selected Tests" item from the context menu. Tell us if the test runs normally on your machine.
'
Open the command line (cmd.exe). Navigate to the repository root directory. Run the following command:
The "files.txt" file should be created in the repository root folder. Share this file with us.
To capture a screencast you may use, for instance, the free Jing tool from TechSmith.
I look forward to hearing from you!
Hello Alex.
Thank you for the response. It looks like the problem is not related to the CodeRush. I cannot run the tests through the Test Explorer either, all "Run" commands are disabled and the progress bar is throbbing even though the tests have been discovered. This persists even after the reinstallation of Windows and VS. I think I'll have to investigate further myself. Thank you for your assistance.
Hi Alexei,
Thank you for the update.
I'm concerned to hear that you are experiencing a problem with running tests. When I was trying to reproduce this problem, I noticed that the Visual Studio test explorer doesn't allow running tests before it has not found all tests within a solution. But, the Roslyn project is quite large so it takes about 30 min before I can run any test on my machine via Test Explorer.
Could you provide us with CodeRush log files? They may shade some light on the cause of the problem. You can find them at the following location: %LocalAppData%\CodeRush\Logs.
Hi.
I have an older branch of Roslyn where the projects don't include xUnit VS integration, so the tests aren't available in Test Explorer, but Test Runner can run any tests without any extraordinary delay.
Anyway, I've attached the latest log. All other TestRunner logs look like that.
Bingo! I've replaced the Newtonsoft.Json.dll in the rmyfztmi.fjf extension folder with version 8.0.3, and everything started working again. The VS integration bundled with Roslyn was a red herring.
Alas, that wasn't that easy. This only works if you load VS and the solution first, then swap the dll and start running tests.
Hi Alexei,
Thank you for the update and providing the log file. It has been very helpful.
I have managed to reproduce the problem with the Newtonsoft.Json.dll file locally. We are researching the cause of this issue. You'll be notified when we prepare a fix.
This started happening to me too.
Hi Ondřej,
Could you clarify if you have experienced trouble with running xunit tests within the Roslyn solution? Also, please provide us with CodeRush log files. You can find them at the following location: %LocalAppData%\CodeRush\Logs.