Our small team currently has a weird issue with Chutzpah. Sometimes, when opening a particular solution, we will repeatedly get "Cannot Connect To Sql Server" error dialogs, followed by a number of "Object Reference Not Set" error dialogs. Other solution files work fine.
This of course looks very much like some weird problem in our .sln file, and that's probably the root cause.
However, when I attached a second instance as a debugger, I noticed the error occuring with a call-stack originating in Chutzpah: It seems that the Chutzpah test-discoverer is a bit too liberal in searching for test-files. So while we'll probably be able to fix our immediate problem somewhere in our .sln or .suo file, there's still quite a decent performance gain to be had in Chutzpah.
I'm guessing this is not really intended behavior.
We first noticed this error in 3.2.1, and I've just updated to 3.2.2, which doesnt seem to fix it.
The full call-stack at the time of the error is attached
This of course looks very much like some weird problem in our .sln file, and that's probably the root cause.
However, when I attached a second instance as a debugger, I noticed the error occuring with a call-stack originating in Chutzpah: It seems that the Chutzpah test-discoverer is a bit too liberal in searching for test-files. So while we'll probably be able to fix our immediate problem somewhere in our .sln or .suo file, there's still quite a decent performance gain to be had in Chutzpah.
I'm guessing this is not really intended behavior.
We first noticed this error in 3.2.1, and I've just updated to 3.2.2, which doesnt seem to fix it.
The full call-stack at the time of the error is attached