db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1462) Test harness incorrectly catches db.lck WARNINGS generated during STORE tests and lists the tests as failed in *_fail.txt.
Date Mon, 31 Jul 2006 19:58:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1462?page=all ]

Andrew McIntyre resolved DERBY-1462.

    Fix Version/s:
       Resolution: Fixed
       Derby Info:   (was: [Patch Available])

Committed to trunk with revision 427237. It would be nice if there was a way that we could
tag this for cleanup when it comes time to remove support with jdk1.3, like e.g. including
[JDK13CLEANUP] in the comments.

> 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
>          Issue Type: Test
>          Components: Test
>    Affects Versions:,,,,,,
>         Environment: IBM 1.3.1 JRE for LINUX (and possibly other JRE 1.3.1 environments)
>            Reporter: Stan Bradbury
>         Assigned To: Myrna van Lunteren
>            Priority: Minor
>             Fix For:
>         Attachments: DERBY-1462_102_20060713.diff, DERBY-1462_102_20060713.stat, DERBY-1462_102_20060730.diff
> 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


View raw message