db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2038) lang/releaseCompileLocks.sql and lang/closed.java fail under JDK 1.6 in insane mode
Date Thu, 09 Nov 2006 10:56:37 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2038?page=all ]

Knut Anders Hatlen updated DERBY-2038:
--------------------------------------

    Attachment: derby-2038.diff
                derby-2038.stat

The attached patch makes the tests run cleanly by removing the lines of the stack traces that
are different in sane and insane mode.

> lang/releaseCompileLocks.sql and lang/closed.java fail under JDK 1.6 in insane mode
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-2038
>                 URL: http://issues.apache.org/jira/browse/DERBY-2038
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure, Test
>    Affects Versions: 10.3.0.0
>         Environment: JDK 1.6, insane build of Derby
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: derby-2038.diff, derby-2038.stat
>
>
> These tests fail on all platforms with JDK 1.6 when run against an insane build of Derby.
They don't fail when run against a sane build. See for instance http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/sparc/469556-derbyall_diff.txt
> ********* Diff file derbyall/derbylang/closed.diff
> *** Start: closed jdk1.6.0-rc derbyall:derbylang 2006-11-01 05:42:42 ***
> 17 del
> < 	... 10 more
> 17a17
> > 	... 11 more
> 25 del
> < 	... 10 more
> 25a25
> > 	... 11 more
> Test Failed.
> *** End:   closed jdk1.6.0-rc derbyall:derbylang 2006-11-01 05:42:55 ***
> ********* Diff file derbyall/derbylang/releaseCompileLocks.diff
> *** Start: releaseCompileLocks jdk1.6.0-rc derbyall:derbylang 2006-11-01 06:11:35 ***
> 50 del
> < 	... 28 more
> 50a50
> > 	... 29 more
> 70 del
> < 	... 28 more
> 70a70
> > 	... 29 more
> Test Failed.
> The problem seems to be that the number of stack trace elements printed is different
for sane and insane builds.

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

        

Mime
View raw message