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 "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2006/07/28 20:45:14 UTC

[jira] Commented: (DERBY-1607) new j9 canons required/canons need to be removed to catch up to changes to 7/27/06.

    [ http://issues.apache.org/jira/browse/DERBY-1607?page=comments#action_12424147 ] 
            
Myrna van Lunteren commented on DERBY-1607:
-------------------------------------------

lang/procedureInTrigger.sql is running a similar problem with wctme5.7 as jdk16 as per DERBY-1585. Leaving up to a possible committer to decide whether to check-in the canon in the patch that will have to be removed again once DERBY-1585 gets fixed, or have a known failure cluttering up the test run. (I vote for check in, but can be persuaded as a check-in may suggest to the unwary that the behavior is correct).

> new j9 canons required/canons need to be removed to catch up to changes to 7/27/06.
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-1607
>                 URL: http://issues.apache.org/jira/browse/DERBY-1607
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.0.0
>            Reporter: Myrna van Lunteren
>         Assigned To: Myrna van Lunteren
>            Priority: Trivial
>             Fix For: 10.2.0.0
>
>         Attachments: DERBY_1607_102_20060728.diff, DERBY_1607_102_20060728.stat
>
>
> There are some newer failures with wctme5.7 & wsdd5.6 that are just due to canon maintenance.
> - lang/aggregate.sql - needs a new j9_13 and j9_22 canon
> - lang/ejbql.sql - j9_13 canon can be removed (there is no j9_22 canon)
> - lang/distinct.sql - needs new j9_22 canon
> - nist/dml099.sql - j9_13 canon can be removed
> - lang/procedureInTrigger.sql - needs a j9_22 canon
>     note, this last test also suffers from DERBY-1605.

-- 
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