Complete browser log output when process isn't started

[ghost]

I was working on litixsoft/karma-detect-browsers#22 and travis isn't able to start Chromium successfully (logs).

The process exits "successfully", yet too early and I have no idea why. I cannot recreate it locally and am lacking the logs to investigate. So this is just a feature request to help debugging.

Expected behaviour

Logs as to why the process exited

Actual behaviour

No logs

Environment Details

• Karma version (output of karma --version): taken from package.json "karma": "^0.13.22"
• Relevant part of your karma.config.js file
  I don't know what's relevant so here's the whole thing karma.conf.js

Steps to reproduce the behaviour

I'm not able to reproduce locally, but see the travis logs. I guess one could:

1. create an executable dummy script that simply outputs rubbish and exits with 0
2. name the script chromium-browser
3. add the location of the script as the first element in PATH
4. npm install -D karma-chrome-launcher
5. Add karma-chrome-launcher to the karma.conf.js
6. launch karma with and watch it fail without logs

[wesleycho]

@dignifiedquire can this issue be closed? Looks like the referenced PR is merged.