Console timeout issue with 2.3.0 + Win7


Hi All,

On Windows 7 and using Chutzpah 2.3.0 I now consistently get a timeout error when running tests either from VS 2012 ("Run JS Tests") or from the console if I'm running from a directory other than the one containing chutzpah.console.exe.

I can run tests from VS 2012 in the browser fine, but not if I do /openInBrowser from the console (which tries to run the tests before opening the test harness in the browser). I'm guessing there's some communication issue with phantomjs because I see the phantomjs process start when I trigger the tests.

At least I have two options that work (running in browser from VS 2012 and running from console from the same directory) so it's not a show-stopper for me, just a bit annoying.

Any ideas?

Cheers, Andrew

file attachments

Closed Dec 3, 2013 at 5:50 AM by mmanela
These issues are old, are fixed or the user has no responded. Please file a new issue if you still have a problem.


mmanela wrote Apr 21, 2013 at 9:33 PM

Can you give me a repro of your issue? A zip file containing the scripts that when you run chutzpah on will reproduce the timeout.

andrewgee wrote May 1, 2013 at 12:01 AM

Sorry about the slow reply. Here's a zip of the 2.3.0 nuget package running against phantomjs 1.8.0 (not included because of zip size limitations). Initially when I ran it from the top level:

.\tools\chutzpah.console.exe tests.js

I got the timeout error. I then ran it from the tools directory:

chutzpah.console.exe ..\tests.js

and the tests ran fine. I then tried running form the top level again and it now worked! :-(

I'll try 2.4 and see if that's fixed my problem.

Cheers, Andrew

andrewgee wrote May 1, 2013 at 12:14 AM

PS. 2.4.0 seems to have solved the problem (fingers crossed :-)

mmanela wrote May 1, 2013 at 4:06 AM

Let me know if you still see the issue