[
https://issues.apache.org/jira/browse/DERBY-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710343#action_12710343
]
Kristian Waagan commented on DERBY-4199:
----------------------------------------
Backported to the 10.5 branch with revision 775907.
I verified that the logging worked by looking at some (internal) archives from
Ole's daily testing, where the exceptions logged to file in the fail-directory
matched those reported by Ole's frameworks. I verified it for both failures and
errors.
> Write exceptions to file in the fail directory as they occur with JUnit tests
> -----------------------------------------------------------------------------
>
> Key: DERBY-4199
> URL: https://issues.apache.org/jira/browse/DERBY-4199
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Reporter: Kathey Marsden
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: derby-4199-1a-writeExceptionsToFile.diff,
> derby-4199-1a-writeExceptionsToFile.stat
>
>
> It would be very helpful to write exceptions to the fail directory as they
> oiccur with JUnit tests.
> If tests hang we can still get the failure information and sometimes it is
> just more efficient to be able to see failures as they occur. Kristian
> attached a patch to DERBY-2667 for this but it no longer applies to trunk
> (derby-2667-WriteExceptionsToFileAsTheyHappen.diff).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
