db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4047) tests updatelocks and updatelocksJDBC30.sql are not run anywhere; should get evaluated
Date Fri, 06 Feb 2009 19:31:02 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-4047:
--------------------------------------

    Attachment: DERBY-4047_a.diff

I started with just running the tests and updatelocksJDBC30.out only diffed from the master
in that is now license header information in the output, so I updated the master with revision
741687.
However, updatelocks shows a number of different locking rows. I don't know whether there
is a bug hiding here or no, and would appreciate someone who might know to take a look.
Attaching a patch that shows the new output.

> tests updatelocks and updatelocksJDBC30.sql are not run anywhere; should get evaluated
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-4047
>                 URL: https://issues.apache.org/jira/browse/DERBY-4047
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Priority: Trivial
>         Attachments: DERBY-4047_a.diff
>
>
> I noticed the tests store/updatelocks.sql and store/updatelocksJDBC30.sql are not in
use.
> They should get evaluated for inclusion in the tests - they should either get included
- and preferably converted to junit - or get deleted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message