[ http://issues.apache.org/jira/browse/DERBY-1462?page=all ]
Myrna van Lunteren updated DERBY-1462:
--------------------------------------
Attachment: DERBY-1462_102_20060713.stat
DERBY-1462_102_20060713.diff
Attached patch for 10.2 - DERBY-1462_102_20060713.* - adds _sed.properties
files for all the tests that are listed as failing, plus for st_derby715.java
which also fails.
In addition, I had to modify RunTest.java to pick up the stress_sed.properties
file (which was not happening because the multi test sits in a different
location from the rest of the tests).
Finally I modified 2 build.xmls to no longer need the copyfiles.ant - which is
how other test dirs have their build.xml now. (eliminating the maintenance pain
of coyfiles.ant).
I ran the troublesome test suites with ibm131 and ibm142 on Linux with only
failures in stress multi which appeared to be the known intermittent problem (I
reran that until it passed once...) and is at least not related to this issue.
> Test harness incorrectly catches db.lck WARNINGS generated during STORE tests
> and lists the tests as failed in *_fail.txt.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1462
> URL: http://issues.apache.org/jira/browse/DERBY-1462
> Project: Derby
> Type: Test
> Components: Test
> Versions: 10.1.2.5, 10.1.2.4, 10.1.2.3, 10.1.2.2, 10.1.2.1, 10.1.3.0,
> 10.1.3.1
> Environment: IBM 1.3.1 JRE for LINUX (and possibly other JRE 1.3.1
> environments)
> Reporter: Stan Bradbury
> Assignee: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1462_102_20060713.diff, DERBY-1462_102_20060713.stat
>
> The following store tests from derbyall do not shutdown cleanly so leave the
> db.lck file on disk. This is OK! It is done by design to test recovery. THE
> PROBLEM, when run on Linux using IBM JRE 1.3.1 sp 10 the test harness 'sees'
> the warnings and lists the tests as having failed. The harness should ignore
> this warnings as the tests proceed and complete cleanly.
> Tests INCORRECLTY reported as failed:
> derbyall/derbynetclientmats/derbynetmats.fail:stress/stress.multi
> derbyall/derbynetmats/derbynetmats.fail:stress/stress.multi
> derbyall/storeall/storeall.fail:storetests/st_1.sql
> derbyall/storeall/storeall.fail:unit/recoveryTest.unit
> erbyall/storeall/storeall.fail:store/LogChecksumRecovery.java
> derbyall/storeall/storeall.fail:store/LogChecksumRecovery1.java
> erbyall/storeall/storeall.fail:store/MaxLogNumberRecovery.java
> derbyall/storeall/storeall.fail:store/oc_rec1.java
> derbyall/storeall/storeall.fail:store/oc_rec2.java
> derbyall/storeall/storeall.fail:store/oc_rec3.java
> derbyall/storeall/storeall.fail:store/oc_rec4.java
> derbyall/storeall/storeall.fail:store/dropcrash.java
> derbyall/storeall/storeall.fail:store/dropcrash2.java
> Example Error message:
> WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the
> database
> csf:/local1/131TST/Store1/storeall/storerecovery/storerecovery/wombat even
> though Derby (instance xxxxFILTERED-UUIDxxxx) may still be active. Only one
> instance of Derby should boot a database at a time. Severe and
> non-recoverable corruption can result and may have already occurred.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
