1

Resolved

Debug unit test doesn't run the test

description

This is intermittent. VS 2013. Easiest way to reproduce:

Fresh VS instance
Load azure solution
test_batch_insert

Workspace changes to debugging and then back. Test isn't run.

Null reference exception in the output window. In test executor.

Repeating the operation usually works.

comments

huguesv wrote Aug 14, 2013 at 8:21 PM

Still happens sometimes with build CL33074. VS2012.

huguesv wrote Sep 20, 2013 at 10:06 PM

Still happens sometimes with Sept 20th build, VS2013.

Zooba wrote Oct 3, 2013 at 4:23 PM

This should be fixed with the longer delay before calling RefreshIsCurrent.

Zooba wrote Feb 3 at 8:55 PM

Still occurring in latest builds.

Zooba wrote Mar 11 at 10:43 PM

Cannot repro - deferring to post-beta.

Zooba wrote Mar 20 at 5:51 PM

This is because the executor creates a race condition on a dictionary, which throws NullReferenceException while setting it.

We should make VisualStudioApp.FromCommandLineArgs non-reentrant.