PhantomJS timeout in Ubuntu

[kcz]

When I try to run grunt jasmine, it failed, due to a timeout, in Ubuntu 10.04 with PhantomJS 1.5.
But the same project worked well in my Mac 10.7.3.

The error message is as follows:

Running "jasmine:all" (jasmine) task
Running specs for index.html

<WARN> PhantomJS timed out, possibly due to an unfinished async spec. Use --force to continue. </WARN>

Aborted due to warnings.

In order to debug, I replaced my project with jasmine demo from official site. The same phenomenon happened again.
Here is the minimized project to indicate problem:
http://kcz.me/test/grunt-jasmine.zip

Maybe the reason comes from phantomJS version. Is there anyone know where I can download PhantomJS 1.3 since that there is no download link in googlecode.

Thanks.

[creynders]

I have no problems running your test on Mac.
There are some issues with phantomJS v1.5 on windows too.
I have no idea what we can do about it, though.

[Jontyy]

I'm getting the same error, I'm on 12.04 with PhantomJS 1.5.
I can run the qunit task fine though.

[axelhzf]

Same error on OS X with phantomjs 1.5

[creynders]

@axelhzf could you provide me with a barebones setup that fails? I'm on OS X as well and have so far not encountered any problems.

[axelhzf]

It was a problem of my test runner configuration, I was using a HtmlReporter. When I delete this reporter it worked. My final configuration is:

<script type="text/javascript">
    jasmine.getEnv().execute();
</script>

[mattd]

I ran kcz's test project on OSX Lion, and I get the same error. A project I've been working on is showing the same results.

[creynders]

@mattd what version of PhantomJS are you using? 1.5? I'm still on v1.4.1 and have no problems.
This is a really unfortunate situation. Something changed from v1.4.x to v1.5, but I have no idea what. Could be PhantomJS is WAI and my code simply benefits from a previous PhantomJS bug - or a new bug was introduced in PhantomJS. It's however very hard to find out what is going wrong since there's a whole stack of tech involved: grunt, phantomjs, jasmine, my plugin, and a bunch of other node modules.

@ariya is there some way we could join forces on this and find out what's going wrong? I can mail you more specifics about how my grunt plugin uses phantomjs

[Aaronius]

Hey creynders, thanks for your work on this and it's good to see you on the interwebs again. I noticed on my setup with Windows 7 that Phantom 1.4 and 1.5 both time out but 1.3 works. Using grunt-mocha all three time out. The tasks are so similar I don't know why I see different results. Sorry, I don't have an answer yet either.

[mattd]

@creynders Yeah, the size of the stack is what had me scratching my head.

So I finally got my setup working after many hours. My notes:

• @kcz 's test project is definitely broken on 1.5. I downgraded to 1.4.1 and it works flawlessly.
• After downgrading to 1.4.1, I went back and tried running my project's test suite. While it didn't work, I did finally get some helpful error reporting - specifically, a missing variable. So 1.5 was swallowing the error, 1.4.1 was not.
• I'm using backbone-boilerplate, which includes a skeleton for jasmine tests. It uses upwards-climbing relative paths for scripts, which apparently angers PhantomJS. I symlinked my application directories into my testing root, and everything works flawlessly. I assume that's a bug in PhantomJS and not intentional, so I'll file a bug report for @ariya to weigh in on.

Thanks so much for writing this task - I initially thought I'd have to write it myself. ;)

[mattd]

For reference, the bug report. http://code.google.com/p/phantomjs/issues/detail?id=583

[creynders]

@mattd wow, thanks a lot for the hard work! I'll keep an eye on your bug report and see if there is something I do have to do.

[creynders]

@kcz @mattd @axelhzf @Aaronius @Jontyy Have you guys tried PhantomJS v1.6 ? With the Grunt Qunit plugin there were similar problems and I just had confirmation from someone that they were solved by updating.

[kcz]

@creynders , thanks for your reminder. But i've got the same error with PhantomJS v1.6 in Ubuntu 10.04. How about other guys?

[PhillyWebGuy]

Same problem here, PhantomJS 1.5.1, Ubuntu 12.04. Would love to figure this out.