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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2007/05/05 04:12:15 UTC
[jira] Created: (DERBY-2614) improve upgrade junit test to not lose
info written to derby.log
improve upgrade junit test to not lose info written to derby.log
----------------------------------------------------------------
Key: DERBY-2614
URL: https://issues.apache.org/jira/browse/DERBY-2614
Project: Derby
Issue Type: Improvement
Components: Test
Affects Versions: 10.3.0.0
Reporter: Mike Matrigali
When upgrade tests are run against multiple jar versions it looks like derby.log gets overwritten at some point, so
history of previous errors is overwritten. I am not sure when this happens. I discovered it when I was trying to
debug a problem that happened with a 10.0 database while I had 5 other jar files in my path. I noticed that when I removed
all the other jar files in the path that then the error encountered with the 10.0 database was still in the derby.log in the
system directory.
To reproduce the problem I was running upgrade tests on 535429 version of the trunk with jars in my test path for the following releases
10.0.2.1 10.1.1.0 10.1.2.1 10.1.3.1 10.2.1.6 10.2.2.0. I was encountering DERBY-2613. The stack trace printed from both
junit.swingui.TestRunner and junit.textui.TestRunner wasn't particularly useful. It looks like a nested exception was not printed. When
I went to look for the error in the derby.log after running full set of tests I could not find it. I deleted all libs except for 10.0.2.1 and reran
and then did find the error in the derby.log along with the nested exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2614) improve upgrade junit test to not
lose info written to derby.log
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-2614.
-----------------------------------
Resolution: Fixed
Assignee: Manjula Kutty
Manjula fixed the tests to save off the derby.log on failure.
> improve upgrade junit test to not lose info written to derby.log
> ----------------------------------------------------------------
>
> Key: DERBY-2614
> URL: https://issues.apache.org/jira/browse/DERBY-2614
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Mike Matrigali
> Assignee: Manjula Kutty
>
> When upgrade tests are run against multiple jar versions it looks like derby.log gets overwritten at some point, so
> history of previous errors is overwritten. I am not sure when this happens. I discovered it when I was trying to
> debug a problem that happened with a 10.0 database while I had 5 other jar files in my path. I noticed that when I removed
> all the other jar files in the path that then the error encountered with the 10.0 database was still in the derby.log in the
> system directory.
> To reproduce the problem I was running upgrade tests on 535429 version of the trunk with jars in my test path for the following releases
> 10.0.2.1 10.1.1.0 10.1.2.1 10.1.3.1 10.2.1.6 10.2.2.0. I was encountering DERBY-2613. The stack trace printed from both
> junit.swingui.TestRunner and junit.textui.TestRunner wasn't particularly useful. It looks like a nested exception was not printed. When
> I went to look for the error in the derby.log after running full set of tests I could not find it. I deleted all libs except for 10.0.2.1 and reran
> and then did find the error in the derby.log along with the nested exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.