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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/11/24 09:09:13 UTC
[jira] Updated: (DERBY-4912) Instability in Derby2017LayerBTest
[ https://issues.apache.org/jira/browse/DERBY-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4912:
-----------------------------------
Attachment: derby-4912-1a-unorderedAssert.diff
Attached patch 1a, which makes the result set assert ignore the order of the rows.
Committed to trunk with revision 1038514. Will backport tomorrow.
This is another case where it would have been interesting to understand why Dag is the only one (so far) seeing a different ordering of the result. Labeled as instability, I assume he's not even seeing it consistently.
Dag, did this test ever fail when run standalone, or did you only see the problem when running suites.All?
(the latter may point towards memory related issues affecting the order)
> Instability in Derby2017LayerBTest
> ----------------------------------
>
> Key: DERBY-4912
> URL: https://issues.apache.org/jira/browse/DERBY-4912
> Project: Derby
> Issue Type: Bug
> Components: Test
> Reporter: Dag H. Wanvik
> Assignee: Kristian Waagan
> Attachments: derby-4912-1a-unorderedAssert.diff
>
>
> Seen on 10.7 RC1:
> testFailedStreamInsertBinaryAutoCommitRollbackOnError(org.apache.derbyTesting.functionTests.tests.jdbc4.Derby2017LayerBTest) FAILURE:
> junit.framework.AssertionFailedError: Column value mismatch @ column 'B', row 1:
> Expected: >5468697320697320726f772031<
> Found: >5468697320697320726f772036<
> at junit.framework.Assert.fail(Assert.java:47)
> at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1213)
> at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1125)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1012)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:935)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:892)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:850)
> at org.apache.derbyTesting.functionTests.tests.jdbc4.Derby2017LayerBTest.doInsertTest(Derby2017LayerBTest.java:493)
> at org.apache.derbyTesting.functionTests.tests.jdbc4.Derby2017LayerBTest.testFailedStreamInsertBinaryAutoCommitRollbackOnError(Derby2017LayerBTest.java:315)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.