phantomjs timeout

[mats]

Try their mailing list?

https://groups.google.com/forum/#!forum/phantomjs

[AaronTovo]

I posted it to the phantomjs forum: https://groups.google.com/forum/#!topic ... iDj7JvZ_Mw

[mats]

Any progress on this?

[AaronTovo]

No. There haven't been any responses to my post on the phantomjs forum. I've been working on other stuff hoping that a quick and easy solution would appear on that forum. I might try using Selenium instead of phantomjs.

BTW, congrats on a pair of fine goals in today's game!

[mats]

Ok, hoping it'll be resolved soon.

Goals last night were good, too bad it meant nothing

[AaronTovo]

I configured the server so that it doesn't require a password and I get the same timeout message. However Fiddler shows very different http requests in that case.

When I run the server with authentication I see that all of the http get requests are loading the authentication page for my app. But I don't see anything that loads siesta files. It never gets past the login page and never loads any siesta files.

When I run the server with authentication disabled I see the http get requests are loading the siesta test page. It's as though everything is fine but phantomjs just needs a command to tell it to run the tests. The index.js page is loaded, but none of my tests are loaded and nothing from my app is loaded.

[AaronTovo]

Progress! I had my code loading siesta-1.0.8-lite instead of siesta-1.0.8-trial. (I've got back and forth a couple of time to check things out)

Now it works with anonymous login (ie, authentication turned off) but it still fails with authentication turned on.

[mats]

Glad to hear good news, so now you can at least use phantom as intended?

[AaronTovo]

Yes, I think we can turn of authentication during the CI builds which is the intended use. And it will probably be a little better without the auth because we don't want to run code (ie, the code that actually does the authenticating) that we aren't actually testing.