You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/04/29 17:54:30 UTC
[jira] Created: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
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
Priority: Minor
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.
[jira] Updated: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4199:
----------------------------------
Derby Categories: [High Value Fix]
> 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
> Priority: Minor
>
> 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.
[jira] Resolved: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-4199.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Derby Info: (was: [Patch Available])
Committed patch 1a to trunk with revision 774729.
It has only gone through manual testing, I'll verify it in one of the nightly tests.
The patch can be merged with 10.5 cleanly, but merging it with 10.4 requires a separate patch or possibly backporting of an additional change.
I do plan to backport to 10.5.
> 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.
[jira] Assigned: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan reassigned DERBY-4199:
--------------------------------------
Assignee: Kristian Waagan
> 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
>
> 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.
[jira] Updated: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4199:
-----------------------------------
Derby Info: [Patch Available]
> 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
> 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.
[jira] Commented: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-4199) Write exceptions to file in the fail
directory as they occur with JUnit tests
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4199:
-----------------------------------
Attachment: derby-4199-1a-writeExceptionsToFile.stat
derby-4199-1a-writeExceptionsToFile.diff
I refreshed, and changed, the original patch.
Patch 1a will log exceptions to a file called 'error-stacktrace.out' in the same directory as derby.log and the database are saved. If copying the log file or the database fail, that exception will also be logged to the file.
To avoid overwriting potentially valuable information, the file is opened in append mode. The time and date are written as a header before the exception stack trace is written.
I have tested the patch manually (by throwing an exception in a test, and also by removing the write privileges on the derby.log file), and will start the regression tests.
Patch ready for review.
> 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
> 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.