You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an error occurs, karma uses log.error() to print the error. However it writes to stdout instead of stderr. Moreover, no error exist code is returned.
The text was updated successfully, but these errors were encountered:
Writing errors into stderr is easy, I think logger should be responsible for that. The default console logger should just use console.error for errors, which writes to stderr.
Handling the exit code is little bit more complicated. I think it should not be a responsibility of the logger - logger should just output logs. We should probably emit error event on the global emitter and listen on this event and 1/ clean up (eg. kill all launchers) 2/ call done callback (which is process.exit(code) by default, but could also be just a function in the case something is calling karma programatically)
Log errors, by default, to a new jog4js appender, the std_appender. This
new appender logs ERROR level events with console.error, and all other
events with console.log.
Closeskarma-runner#1011
When an error occurs, karma uses
log.error()
to print the error. However it writes tostdout
instead ofstderr
. Moreover, no error exist code is returned.The text was updated successfully, but these errors were encountered: