Skip to main content
brian_thomas2
Adobe Employee
Adobe Employee
Aug 21, 2009 8:38 PM UTC
Answered

Errors in RunListeners

I recently ran into a situation where one of my RunListeners was throwing an error (attempted to create invalid XML - oops). This produced some very strange results: my RunListener stopped receiving callbacks after this happened. I debugged it down to the line that was throwing the error, and noticed it was getting sucked up into this "SafeNotifier":

Main Thread (Suspended)

SafeNotifier/run

org.flexunit.runner.notification::RunNotifier/fireTestFailure

org.flexunit.internals.runners.model::EachTestNotifier/addFailure

org.flexunit.runners::BlockFlexUnit4ClassRunner/handleBlockComplete

org.flexunit.token::AsyncTestToken/sendResult

etc...

Is there any way around this? How might I go about catching an error in my RunListener? Or even better, letting the error cause a failure in the test that the current call into the RunListener is assocated with?

Thanks!

Brian

This topic is closed to new replies. Start a new post to keep the conversation going.
mlabriolaCorrect answer
Participating Frequently
Aug 21, 2009 8:59 PM UTC

Here is the bug:

https://bugs.adobe.com/jira/browse/FXU-32

I will add your comments from this thread to it.

3 replies

Participating Frequently
Aug 21, 2009 8:42 PM UTC

Brian,

That is actually one of the tasks in our jira at the moment is to separate those out to make it clear what is happening. Also to ensure that a rouge listener could be removed if it is throwing errors.

Mike

Translate
brian_thomas2
Adobe Employee
Adobe Employee
Aug 21, 2009 8:52 PM UTC

Excellent! Do you have the bug id for that? I'd like to make sure I'm watching it.

Thanks,

Brian

Translate
mlabriolaCorrect answer
Participating Frequently
Aug 21, 2009 8:59 PM UTC

Here is the bug:

https://bugs.adobe.com/jira/browse/FXU-32

I will add your comments from this thread to it.

Translate