Currently clj-gatling error handler catches only errors deriving from Exception. Other errors will not be catched and those will be handled using https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.UncaughtExceptionHandler.html. If uncaught exception handler is not set (the default behaviour) the exception stack trace is written to stderr. At the moment clj-gatling does not set this handler and uses the default behaviour.
Clojure asserts use AssertionError which does not derive from Exception. Therefore assertion errors do not end to any reports. Those should be catched by clj-gatling and handled in the same manner as other exceptions.
Currently
clj-gatling
error handler catches only errors deriving fromException
. Other errors will not be catched and those will be handled using https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.UncaughtExceptionHandler.html. If uncaught exception handler is not set (the default behaviour) the exception stack trace is written to stderr. At the momentclj-gatling
does not set this handler and uses the default behaviour.Clojure
assert
s use AssertionError which does not derive fromException
. Therefore assertion errors do not end to any reports. Those should be catched byclj-gatling
and handled in the same manner as other exceptions.