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-4460) test_031_derby_4413 failed in nightly regression run : ComparisonFailure: expected:<1> but was:<2>
Date Tue, 01 Dec 2009 23:33:20 GMT

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

Knut Anders Hatlen updated DERBY-4460:
--------------------------------------

    Attachment: orderby.diff

The attached patch adds an ORDER BY clause to the query that checks the contents of the table
in order to guarantee a specific ordering. Then the test passes on Java 1.5, 1.6 and 1.7 on
my system (without the patch it fails on 1.5).

The root cause appears to be the same as in DERBY-4457. Now that DERBY-4442 ensures that the
generated columns are added to a node on top of the SelectNode in the INSERT statement, SELECT
DISTINCT can be performed with a hash scan instead of a sort, and the order in which the rows
are inserted depends on the JVM's hash table implementation.

> test_031_derby_4413 failed in nightly regression run : ComparisonFailure: expected:<1>
but was:<2>
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4460
>                 URL: https://issues.apache.org/jira/browse/DERBY-4460
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.0.0
>         Environment: ibm15 jvm on windows
> ibm142 jvm on linux
> ibm15 jvm on linux
>            Reporter: Mike Matrigali
>            Assignee: Knut Anders Hatlen
>         Attachments: orderby.diff
>
>
> Failed in full nightly run along with the already fixed testDistinctInsertWithGeneratedColumn
failure.  
> 2) test_031_derby_4413(org.apache.derbyTesting.functionTests.tests.lang.GeneratedColumnsTest)junit.framework.ComparisonFailure:
expected:<1> but was:<2>
> 	at org.apache.derbyTesting.functionTests.tests.lang.GeneratedColumnsHelper.assertResults(GeneratedColumnsHelper.java:346)
> 	at org.apache.derbyTesting.functionTests.tests.lang.GeneratedColumnsHelper.assertResults(GeneratedColumnsHelper.java:310)
> 	at org.apache.derbyTesting.functionTests.tests.lang.GeneratedColumnsTest.test_031_derby_4413(GeneratedColumnsTest.java:5442)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

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