On Sep 26 2017, at 10:08 am, Thomas Kluyver <[email protected]> wrote: 
I'd make an educated guess that Toree is not signalling errors in the way you expect.

I can confirm that the Toree kernel does not signal errors properly.  I don't know what exactly it does wrong, but the notebook doesn't get outputs of type "error" after problems occur.  Instead the stack traces appear in a standard output cell.

We ran into this problem in our notebook testing infrastruture.  Our solution was to search for "StackTrace" in the output cell, and assume that this indicated an error.  Maybe that would work for you?

Robert

--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/local-24435c24-e78d%40nylas-mail.nylas.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to