In <this> thread, <@U013DCMNJTH> said, &gt; peopl...

# coroutines

[Doug McCluer]

In this thread, @Dmitry Khalanskiy [JB] said,

people do write code without structured concurrency support. To help them find the places where their code crashes, we've added special behavior: runTest keeps track of all unhandled exceptions in the system, and if there are any, reports them somewhere, even if they are unrelated to the test

How can I find out where those unhandled exceptions are reported?

[Dmitry Khalanskiy [JB]]

They are thrown from runTest. Either at the end of the test where unhandled exceptions happened, or at some point during the later tests.

[Doug McCluer]

When I run my tests I see in the log output that one failed due to UncaughtExceptionsBeforeTest, but it doesn't tell me what exception was uncaught, or what test produced it and I don't see a exception previously reported in the log. Where should I look to learn what the exception was which went uncaught?

[Dmitry Khalanskiy [JB]]

The exception that led to the error is added as a suppressed exception to UncaughtExceptionsBeforeTest, so it should be included in the log along with the stacktrace of the UncaughtExceptionsBeforeTest.

[Doug McCluer]

Ok, I think my stacktrace is getting truncated
Thank you!