busterjs/buster — Issue #104: Chrome results mixed with other browser's results
Author: jodal
Created: 2012-02-23 14:16:32+00:00
State: open

I'm running tests in a loop on changes to source or test files using `inotifywait`. I connected three slaves to the server, and Chrome is behaving very inconsistent compared to Firefox and Opera.

Below I've pasted the output of five test runs with identical code.

- The first run works as expected.

- In the second run, Firefox reports about twice as many tests executed as normal, while Chrome is listed with 0 tests executed. Buster didn't return control to my script, so I had to hit Ctrl+C.

- In the third run, Firefox is back to normal, and Chrome is never listed. Ctrl+C again.

- Same in the fourth run.

- In the fifth run, everything's working again. I believe I reconnected Chrome before the fifth run.

What I find most interesting here is the second run, where it may seem as Chrome's test results are mixed with those of Firefox.

```
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
test/ CREATE 4913
Opera 11.61 Linux: ................
Firefox 11.0 Linux: ................
Chrome 17.0.963.56 Linux: ................
21 test cases, 48 tests, 84 assertions, 0 failures, 0 errors, 0 timeouts

Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
test/ CREATE 4913
Firefox 11.0 Linux: ..........................
Opera 11.61 Linux: ................
Chrome 17.0.963.56 Linux:
21 test cases, 48 tests, 84 assertions, 0 failures, 0 errors, 0 timeouts
^C
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
test/ CREATE 4913
Firefox 11.0 Linux: ................
Opera 11.61 Linux: ................
^C
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
test/ CREATE 4913
Chrome 17.0.963.56 Linux: ................
Firefox 11.0 Linux: ................
Opera 11.61 Linux: ................
21 test cases, 48 tests, 84 assertions, 0 failures, 0 errors, 0 timeouts

Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
# and so on...
```