search

skytreader / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
0 stars 0 forks source link

Tests hang in 1.3.3c #282

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run our tests in 1.3.3c
2. At the same point each time, the tests hang and timeout

What is the expected output? What do you see instead?
I expect the tests to pass. They work fine with a previous 1.3.3 snapshot jar 
that we built ourselves several months ago.

What version of the product are you using? On what operating system?
1.3.3c on Mac w/Safari

Please provide any additional information below.
These tests work just fine with a previous 1.3.3 snapshot that we built 
ourselves previously. We are using Maven to run the tests. We run the tests 
using our custom 1.3.3 snapshot jar, and all tests pass. I switch to the 1.3.3c 
jar, and the tests always stop at this same spot (we run tests in about 15 
projects, it always stops in this project).

I can't tell from the output what went wrong. Attached is the output. I just 
included the last 2 projects, since all the previous ones work fine in both.

We run the server locally like this:

java -jar /Users/logan/projects/tools/jstestdriver/jstestdriver-1.3.3c.jar 
--port 4224 --runnerMode DEBUG | tee jstd.txt
The tests are run from Maven like this:

      <plugin>
        <groupId>com.google.jstestdriver</groupId>
        <artifactId>maven-jstestdriver-plugin</artifactId>
        <version>1.3.2.1</version>
        <executions>
          <execution>
            <id>run-tests</id>
            <phase>test</phase>
            <goals>
              <goal>test</goal>
            </goals>
            <configuration>
              <reset>${jstestdriver.reset}</reset>
              <captureConsole>false</captureConsole>
              <testOutput>${basedir}/target/test-reports</testOutput>
              <config>${basedir}/target/test-resources/jsTestDriver.conf</config>
<!--              <verbose>true</verbose>-->
            </configuration>
          </execution>
        </executions>
      </plugin>

Original issue reported on code.google.com by RedB...@gmail.com on 18 Oct 2011 at 9:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Here is our jsTestDriver.conf, auto generated from a previous build step.

Original comment by RedB...@gmail.com on 18 Oct 2011 at 9:45

Attachments:

GoogleCodeExporter commented 9 years ago 
Works in Chrome & Firefox on Mac, only fails in Safari. Works in Chrome & 
Firefox on Linux.

This is the error in the Safari console:
Failed to load resource: the server responded with a status of 413 (Request 
Entity Too Large)  load

The load link looks like this: 
http://127.0.0.1:4224/slave/id/1319036578694/rt/CLIENT/mode/quirks/page/RUNNER/u
pload_size/50/refresh/1319040153694/load_type/load/refresh/1319040156265/load_ty
pe/preload/testcase_id/default/refresh/1319040185251/load_type/load/refresh/1319
040186772/load_type/preload/testcase_id/default/refresh/1319040213292/load_type/
load/refresh/1319040214825/load_type/preload/testcase_id/default/refresh/1319040
266726/load_type/load/refresh/1319040267853/load_type/preload/testcase_id/defaul
t/refresh/1319040272588/load_type/load/refresh/1319040273627/load_type/preload/t
estcase_id/default/refresh/1319040278710/load_type/load/refresh/1319040280281/lo
ad_type/preload/testcase_id/default/refresh/1319040286687/load_type/load/refresh
/1319040287788/load_type/preload/testcase_id/default/refresh/1319040292132/load_
type/load/refresh/1319040293210/load_type/preload/testcase_id/default/refresh/13
19040299613/load_type/load/refresh/1319040301277/load_type/preload/testcase_id/d
efault/refresh/1319040309078/load_type/load/refresh/1319040311170/load_type/prel
oad/testcase_id/default/refresh/1319040316620/load_type/load/refresh/13190403176
76/load_type/preload/testcase_id/default/refresh/1319040321882/load_type/load/re
fresh/1319040323520/load_type/preload/testcase_id/default/refresh/1319040329023/
load_type/load/refresh/1319040330753/load_type/preload/testcase_id/default/refre
sh/1319040342503/load_type/load/refresh/1319040345007/load_type/preload/testcase
_id/default/refresh/1319040356082/load_type/load/refresh/1319040357425/load_type
/preload/testcase_id/default/refresh/1319040368381/load_type/load/refresh/131904
0369758/load_type/preload/testcase_id/default/refresh/1319040374995/load_type/lo
ad/refresh/1319040376729/load_type/preload/testcase_id/default/refresh/131904038
4039/load_type/load/refresh/1319040385536/load_type/preload/testcase_id/default/
refresh/1319040392008/load_type/load

Original comment by RedB...@gmail.com on 19 Oct 2011 at 4:09

GoogleCodeExporter commented 9 years ago 
The maven output looks like this:

[INFO] [js-gadget:generate-test-conf {execution: default-generate-test-conf}]
[INFO] [jstestdriver:test {execution: run-tests}]

-------------------------------------------
 J S  T E S T  D R I V E R                 
-------------------------------------------

Firefox: Reset
Firefox: Reset
Chrome: Reset
Chrome: Reset
..................................Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
Safari: Reset
......
until it finally times out

Original comment by RedB...@gmail.com on 19 Oct 2011 at 4:10

GoogleCodeExporter commented 9 years ago 
Since it seemed it only affect Safari, we went ahead and deploy 1.3.3c to our 
Windows 7 test server running Firefox, IE, and Chrome. While it doesn't happen 
every time like it did for my Safari tests, it is happening on all 3 of the 
browsers intermittently, but regularly, enough so that we have to revert back 
to an older version.

Original comment by RedB...@gmail.com on 24 Oct 2011 at 9:27

GoogleCodeExporter commented 9 years ago 
I've got similar or the very same problem.
I get a master jstd node (running on windows) to which I attach few browsers 
from other windows machines.
2 of 5 times I want to run the tests the Chrome browser hangs infinitely on the 
reset procedure. It's always the Chrome browser that runs into the loop.
The problem occurs on jstd 1.3.4-a and jstd 1.3.1 which I previously used.

Original comment by tomasz.c...@codepill.com on 9 Feb 2012 at 1:17

GoogleCodeExporter commented 9 years ago 
I have the same issue with Chrome and Firefox, both on Windows and Ubuntu. The 
reset command doesn't seem to work. I have tried this with the latest master 
commit. 

The browser page says

JsTestDriver
Last:1346256250971 | Next:1998 | Server:Running: command= 
{"command":"reset","parameters":[]}

and the last lines of the jstestdriver output are:

Aug 29, 2012 6:01:27 PM 
com.google.jstestdriver.server.handlers.HeartbeatGetHandler handleIt
FINE: requesting SlaveBrowser(browserInfo=Chrome 21.0.1180.81 Linux,
        id=1346256082431,
        sinceLastCheck=0.187s,
        timeout=30000)
Aug 29, 2012 6:01:27 PM com.google.jstestdriver.CommandTask run
FINE: Starting upload for 1346256082431
Aug 29, 2012 6:01:27 PM com.google.jstestdriver.CommandTask run
FINE: Finished upload for 1346256082431
Aug 29, 2012 6:01:27 PM com.google.jstestdriver.CommandTask run
FINE: Starting {"command":"reset","parameters":[]} for 1346256082431
Aug 29, 2012 6:01:28 PM 
com.google.jstestdriver.server.handlers.BrowserLoggingHandler handleIt
FINE:   [log]
[2012-08-29T16:01:28.071Z] current command reset
Aug 29, 2012 6:01:28 PM 
com.google.jstestdriver.server.handlers.BrowserLoggingHandler handleIt
FINE:   [log]
[2012-08-29T16:01:28.072Z] Replacing 
http://127.0.0.1:4234/slave/page/RUNNER/id/1346256082431/mode/quirks/upload_size
/50#auth/login/refresh/1346256088071/load_type/load
Chrome: Reset
Chrome: Reset
Chrome: Reset
....

Original comment by karel.br...@limecraft.com on 29 Aug 2012 at 4:04

GoogleCodeExporter commented 9 years ago 
I have the same issue with Chrome, Firefox and Safari on 1.3.5.

Caught that with runnerMode  INFO &  --captureConsole on the jstd server.

{"type": "LOG", 
    "response": "{\"source\":1000,\"level\":\"jstestdriver.CommandExecutor\",\"message\":\"Exception TypeError: hostPrefixPageAndPath is null\\nhttp://localhost:42442/static/runner.js(505):\\njstestdriver.ResetCommand.prototype.reset@http://localhost:42442/static/runner.js:505\\nbound@http://localhost:42442/static/jstestdrivernamespace.js:71\\njstestdriver.CommandExecutor.prototype.executeCommand@http://localhost:42442/static/runner.js:2995\\nbound@http://localhost:42442/static/jstestdrivernamespace.js:71\\n.handleSuccess@http://localhost:42442/static/lib/jquery-min.js:141\\n.ajax/w.onreadystatechange@http://localhost:42442/static/lib/jquery-min.js:140\\n\",\"browser\":{\"id\":1362588264983}}", 
    "browser": {
    "id": 1362588264983
}}

Original comment by waswrong...@gmail.com on 6 Mar 2013 at 4:52

GoogleCodeExporter commented 9 years ago 
I have the same issue.  I'm using jstd-maven-plugin 1.3.5.1, running on Windows 
7.  IE8, Chrome, and FireFox were all hanging and JSTD kept issuing command 
"reset".  I have isolated one javascript file.  When I excluded this file jstd 
was able to run through, with error of course.  When I included this file, it 
caused the issue every time.  I'll keep invetigating why this file causing the 
issue, but just want to hear from you guys if you have found resolution for 
your problems

Original comment by wangga...@gmail.com on 18 Jun 2013 at 1:37

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have seen a Chrome slave show this unresponsive behaviour when it runs as a 
background pinned tab: it seems that Chrome deprioritises background tabs (q.v. 
Chromium Issue https://code.google.com/p/chromium/issues/detail?id=87793).

Can you try testing with the slave browser tab in the foreground?

Original comment by andrew.m...@gmail.com on 30 Jul 2013 at 10:14