run-qunit.js waitFor always times out

[ariya]

[email protected] commented:

Which version of PhantomJS are you using? Tip: run 'phantomjs --version'.

DISPLAY=:10 ../tools/phantomjs-1.4.1/linux-x86_64-static/bin/phantomjs --version
1.4.1

What steps will reproduce the problem?

1. us run-qunit.js is an HTML page
   For example:
   DISPLAY=:10 ../tools/phantomjs-1.4.1/linux-x86_64-static/bin/phantomjs ./test-client/scripts/run-qunit.js file:///opt/ci/hudson/workspace/enterprise_test_master/src/test-client/html/prettyTestRunner.html
2. wait

I've tried this with lots of different timeout values and different styles of HTML name (i.e. with and without the file://, abs, and relative paths). I always get a timeout on RHEL 5.4 but Mac OSX is fine.

'waitFor()' inside of run-qunit.js took longer than 300000 ms

What is the expected output? What do you see instead?

[MODULE START] ValidatorTest
[TEST START] ValidatorTest/Email isValid
[ ok ]
[ ok ]

Which operating system are you using?

Linux build-trunk-2 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

CentOS release 5.3 (Final)

Did you use binary PhantomJS or did you compile it from source?

Please provide any additional information below.

Here are the steps I used to build this static version:

[ci@build-trunk-0 phantomjs]$ sudo yum install libXext-devel
[ci@build-trunk-0 phantomjs]$ vi deploy/build-helper.sh
[ci@build-trunk-0 ~]$ git clone git://github.com/ariya/phantomjs.git
[ci@build-trunk-0 ~]$ cd phantomjs/
[ci@build-trunk-0 phantomjs]$ vi deploy/build-helper.sh
[ci@build-trunk-0 phantomjs]$ deploy/build-linux.sh
[ci@build-trunk-0 phantomjs-1.4.1]$ ln -s deploy/Qt-4.7.4/src/3rdparty/webkit/JavaScriptCore
[ci@build-trunk-0 phantomjs-1.4.1]$ cd src/
[ci@build-trunk-0 src]$ cd /usr/lib
[ci@build-trunk-0 lib]$ sudo ln -s libXrender.so.1 libXrender.so
[ci@build-trunk-0 lib]$ cd ../lib64/
[ci@build-trunk-0 lib64]$ sudo ln -s libXrender.so.1 libXrender.so
[ci@build-trunk-0 lib64]$ cd ~/phantomjs-1.4.1/src/

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #394.
🌟   2 people had starred this issue at the time of migration.

[ariya]

[email protected] commented:

I question that I couldn't find an answer to in the FAQ is, "how do I trouble-shoot this?" Can I step thru the JS somehow to see where it is getting hung up? Is a trace of the scripts written out someplace? Do I need to turn on some debugging info?

Thank you.

[ariya]

[email protected] commented:

Can you provide the simplest possible example of the QUnit-based test which can reproduce the problem?

[ariya]

[email protected] commented:

I don't have a simple repro for you - I'll try to get one together. But I believe now that my problem was how I was using require.js and / or co.js I think that you can safely close this issue.

[ariya]

[email protected] commented:

 

 
Metadata Updates

• Status updated: WontFix