ReSharper C++ doesn't detect that test has stopped

using ReSharper C++ 2019.1.3 running in VS Community 2019 (Version 16.5.30002.166)

Sometimes when I stop my a GoogleTest,  test Resharper doesn't detect that test has stopped but Visual Studio did it. I can't stop the test and the problem after that is that I can't run any test and I'm forced to restart Visual Studio to run a test with ReSharper. Is this normal?

I run the test in Debug x64 and my test contains multithreading.

7 comments
Comment actions Permalink

Thanks for the report, I've created a tracking issue - https://youtrack.jetbrains.com/issue/RSRP-479128. If you have any ideas about specific conditions when this happens, please let us know.

1
Comment actions Permalink

I updated my version to 2020.1.2 but the bug reappeared when I modified a .cpp file while I was debugging a unit test. I continue to have this bug and it's freezing my Visual Studio 2019 ! Seems appear only in debug. Visual studio freeze when I'm trying to close session.

0
Comment actions Permalink

Any workaround for this? Other than restarting Visual Studio of course!

0
Comment actions Permalink

Darien Pardinasdiaz We still can't reproduce this. If you have a reproducible case please share.

0
Comment actions Permalink

Igor, I don't have a test case to provide at this moment, but here are the clues I can share right now: 

- Visual Studio 2019 Professional 16.6.3

- Resharper 2020.1.3

- We auto generate Makefile project type with build step that calls our external build scripts. We have production code projects that generate DLLs and testing projects that produce static libs. We then have an executable project that links everything together and wholearchive the testing code into an executable.

I start debugging by clicking on the Debug menu near the TEST_F entry or from the Unit Test Session. If I stop the debugger after editing a file, even without saving it, then the debug session stops, but the test entry in the unit test session keeps spinning forever. Attempting to stop the test just switches between the hand and square (stop) icon, but doesn't do anything. As a workaround, I can click on the test icon near the TEST_F entry and run another session, but the previous one stays there forever in a "Stopping" state.

 

0
Comment actions Permalink

Darien Pardinasdiaz Is this 100% reproducible? We'd appreciate if you could try to reproduce this on a small solution that you can share with us.

0
Comment actions Permalink

For me this is always appends when I modify a file and save it while a test is running. If I don't touch any file, the tests can always be stop.

0

Please sign in to leave a comment.