db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6968) Instability in DatabaseMetaDataTest.testGetBestRowIdentifier
Date Sat, 07 Oct 2017 14:10:00 GMT

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

Rick Hillegas updated DERBY-6968:
---------------------------------
    Attachment: 10.14.1.testResults.0-failures

Attaching 10.14.1.testResults.0-failures, a survey of the errors which Ingo saw.

> Instability in DatabaseMetaDataTest.testGetBestRowIdentifier
> ------------------------------------------------------------
>
>                 Key: DERBY-6968
>                 URL: https://issues.apache.org/jira/browse/DERBY-6968
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Test
>    Affects Versions: 10.14.1.0
>            Reporter: Rick Hillegas
>         Attachments: 10.14.1.testResults.0-failures
>
>
> Ingo reports instabilities in his platform tests of the 10.14.1.0 release candidate.
He sees intermittent failures in DatabaseMetaDataTest.testGetBestRowIdentifier and then subsequent
failures due to poor test case isolation in that test. The test case fails because DatabaseMetaData.getBestRowIdentifier()
sometimes returns rows in a different order than the test expects.
> The JDBC contract for that method does not specify an order for the returned rows. ORDER
BY clauses appear on some but not all the catalog queries in metadata.properties which define
the Derby result.
> I see two ways to address this issue:
> 1) The test could be fixed so that it hand-sorts the returned rows in order to guarantee
deterministic results.
> 2) ORDER BY clauses could be added to all the implicated metadata queries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message