[DERBY-6380] Rolling log files do not get copied in failed directory when a junit test fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.11.1.1
• Component/s: Test
• Urgency: Normal
• Assignee: Myrna van Lunteren
• Reporter: Mamta A. Satoor
• Created: 16/Oct/13 18:01
• Updated: 21/Jan/15 00:23
• Resolved: 02/Dec/13 18:05

Description

DERBY-6350(Provide a rolling file implementation of derby.log) is adding a very useful feature to Derby. To test the feature, I ran the junit suite with rollingFile option as shown below
time java -Dderby.stream.error.style=rollingFile -Dderby.tests.trace=true junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All > runall.out 2>&1
I noticed that even though we are running junit suite with the rollingFile, we still create derby.log(although it was empty) along with expected derby-0.log and so on. I had not expected to see the traditional derby.log when running with rollingFile. In addition, when a test failed, the failed directory had empty derby.log copied but the rolling log files did not get copied. The code changes to copy the rolling log files in case of failure probably need to go into org.apache.derbyTesting.junit.BaseTestCase:runBare() in the "catch (Throwable running) {" section. The log files are crucial to do any test failure debugging and hence should get copied in the failed directory.

Issue Links

• relates to: DERBY-6350 Provide a rolling file implementation of derby.log