search

karma-runner / karma

Spectacular Test Runner for JavaScript
http://karma-runner.github.io
MIT License
11.95k stars 1.71k forks source link

Karma outputs multiple success lines when unit tests are run #1194

Open demisx opened 10 years ago

demisx commented 10 years ago

I use karma for running mocha unit tests. I used to get one success line with cumulative result of all tests. Something like:

PhantomJS 1.9.7 (Mac OS X): Executed 16 of 19 (skipped 3) SUCCESS (0 secs / 0.005

Now, all of a sudden, I am getting multiple success lines starting with test 8:

PhantomJS 1.9.7 (Mac OS X): Executed 8 of 19 (skipped 3) SUCCESS (0 secs / 0.005
PhantomJS 1.9.7 (Mac OS X): Executed 9 of 19 (skipped 3) SUCCESS (0 secs / 0.005
PhantomJS 1.9.7 (Mac OS X): Executed 10 of 19 (skipped 3) SUCCESS (0 secs / 0.00
PhantomJS 1.9.7 (Mac OS X): Executed 11 of 19 (skipped 3) SUCCESS (0 secs / 0.00
PhantomJS 1.9.7 (Mac OS X): Executed 12 of 19 (skipped 3) SUCCESS (0 secs / 0.00
PhantomJS 1.9.7 (Mac OS X): Executed 13 of 19 (skipped 3) SUCCESS (0 secs / 0.00
PhantomJS 1.9.7 (Mac OS X): Executed 14 of 19 (skipped 3) SUCCESS (0 secs / 0.00
PhantomJS 1.9.7 (Mac OS X): Executed 15 of 19 (skipped 3) SUCCESS (0 secs / 0.01
PhantomJS 1.9.7 (Mac OS X): Executed 16 of 19 (skipped 3) SUCCESS (0 secs / 0.01
PhantomJS 1.9.7 (Mac OS X): Executed 16 of 19 (skipped 3) SUCCESS (0.013 secs / 0.01 secs)`

Any idea what could cause this? This is not something code related, since I've tried older commits and they all show multiple lines now. Thanks.

skawaguchi commented 9 years ago

This happens of me on Karma 0.12.31 but not 0.12.29. I've reverted back as a work-around for now.

dshulepov commented 9 years ago

Any fix on this? I just got the same (but on Windows). Just out of the blue it started to output multiple lines for success and errors. No updates or even changes to tests or config files were done between normal work and this buggy behavior. Downgrading to 0.12.29 did not help.

demisx commented 9 years ago

FYi, I am using latest stable karma and haven't seen this issue for a while. Still not sure what caused it.

dshulepov commented 9 years ago

I was using 0.12.31 for a long while until got this issue today. I've updated to 0.12.32 - did not help. I've downgraded to 0.12.29 - did not help. Even rebooted the machine, which often helps on Windows, but not this time.

eihli commented 7 years ago

Just dropping by to say this is still an issue. Just noticed this on 1.6.0. Switched to mocha reporter. Couldn't figure it out. Worked fine yesterday. Put computer to sleep. Opened it up today, got this stuff.

TheMikeSanto commented 6 years ago

Experiencing the same issue on 1.6.0. It wasn't happening, was running tests all day, and then all of a sudden I get this. Pretty inconvenient.

johnjbarton commented 6 years ago

Maybe you have multiple phantomjs instances running?