DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37241 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-25 17:08 ------- Correction: If the usefile attribute of a nested <formatter> element is set to "true" it's addError() and endTestSuite() methods ARE called after a timeout. The addError method is called with an AssertionFailedError with message "Timeout occured" as argument. This is as close as I can get to an entry point for the signal handler you mentioned. I could write a custom JUnitResultFormatter called "JUnitTimeoutListener" that calls the tearDown method of the current test if it's addError method is called with an AssertionFailedError with message "Timeout occured" as argument. Sounds like an ugly hack, but I cannot think of anything better. Or is there a better way? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
