[
https://issues.apache.org/jira/browse/DERBY-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701363#action_12701363
]
Kathey Marsden commented on DERBY-4085:
---------------------------------------
I saw the following failure with IBM 1.4.2 on trunk, Linux. Should I just post
it here or open a separate issue?
1)
testClusMogInMemory(org.apache.derbyTesting.functionTests.tests.memorydb.MogTest)junit.framework.AssertionFailedError:
Error too big;6.911593155944432E-4 >= 1.0E-6, seed=1240288888777
at
org.apache.derbyTesting.functionTests.tests.memorydb.MogTest.compare(MogTest.java:159)
at
org.apache.derbyTesting.functionTests.tests.memorydb.MogTest.doTestClusMog(MogTest.java:143)
at
org.apache.derbyTesting.functionTests.tests.memorydb.MogTest.testClusMogInMemory(MogTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled
Code))
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled
Code))
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled
Code))
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java(Compiled
Code))
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)
> Improve testing of the in-memory back end
> -----------------------------------------
>
> Key: DERBY-4085
> URL: https://issues.apache.org/jira/browse/DERBY-4085
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.6.0.0
>
> Attachments: buildbreak.diff, derby-4085-1a-basic_tests.diff,
> derby-4085-1a-basic_tests.stat, derby-4085-1b-basic_tests.diff,
> derby-4085-2a-mog_func_test.diff, derby-4085-2a-mog_func_test.stat,
> derby-4085-3a-enable_in_suitesAll.diff,
> derby-4085-4a-improved_assertion_reporting.diff,
> derby-4085-5a-report_seed_on_failure.diff
>
>
> The in-memory back end should be tested as part of the standard regression
> tests.
> The following is a good start:
> o simple create / boot test
> o create in-memory db, backup, restore with default storage engine, modify,
> restore with createFrom into memory again
> o add the functional test(s) written by Cheng
> o more unit tests
> On a longer term, we should consider to add the possibility to run all or a
> subset of the general regression tests with the in-memory back end.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
