Skip to main content
brian_thomas2
Adobe Employee
brian_thomas2
Adobe Employee
August 21, 2009
Answered

Errors in RunListeners

  • August 21, 2009
  • 1 reply
  • 1878 views

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 has been closed for replies.
Correct answer mlabriola

Here is the bug:

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

I will add your comments from this thread to it.

1 reply

M
mlabriola
Participating Frequently
August 21, 2009

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

brian_thomas2
Adobe Employee
brian_thomas2Author
Adobe Employee
August 21, 2009

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

Thanks,

Brian

M
mlabriolaCorrect answer
Participating Frequently
August 21, 2009

Here is the bug:

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

I will add your comments from this thread to it.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices