Tests not always running

Can’t get how to exactly reproduce it but it seems to be depending on when runner and compilation starts. If the runner is started and compilation not yet done, then the suit will not run.

--- karma-webpack/example ‹master* M› » karma start                                                                                           127 ↵
WARN [karma]: Port 9876 in use
INFO [karma]: Karma v0.12.1 server started at http://localhost:9877/
INFO [launcher]: Starting browser PhantomJS
Hash: f415b7798b75e5251339
Version: webpack 1.1.0
Time: 6ms
Asset  Size  Chunks       Chunk Names
webpack: bundle is now VALID.
webpack: bundle is now invalid.
2014-03-28 10:29 node[4862] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-28 10:29 node[4862] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
Hash: b79bf627a90c35d205b4
Version: webpack 1.1.0
Time: 32ms
                Asset  Size  Chunks             Chunk Names      
    _js/test/aTest.js  4547       0  [emitted]  test/aTest.js    
       _js/1.chunk.js   117       1  [emitted]                   
_js/test/bTest.coffee  4132       2  [emitted]  test/bTest.coffee
chunk    {0} _js/test/aTest.js (test/aTest.js) 679 [rendered]
    [0] ./test/aTest.js 628 {0} [built]
    [1] ./fixtures/file.js 18 {0} [built]
    [3] ./fixtures/file.coffee 33 {0} [built]
chunk    {1} _js/1.chunk.js 18 {0} {2}
    [2] ./fixtures/file.js?1 18 {1} [built]
chunk    {2} _js/test/bTest.coffee (test/bTest.coffee) 398 [rendered]
    [0] ./test/bTest.coffee 398 {2} [built]
webpack: bundle is now VALID.
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start PhantomJS again (1/2).

I always have this issue then building a bigger bundle.

[okonet]

I’ve solved the issue by increasing the browserNoActivityTimeout in karma config. It seems it took too long to compile a bundle so the browser was killed before the bundle was ready.

[voor]

@okonet 👍 This solved the issue for me as well, is there anyway we can make this fix easier to see? Seems to be pretty common for webpack, browserify, and other pre-compiled processes.