[
https://issues.apache.org/jira/browse/DERBY-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-5865.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.11.0.0
10.10.1.3
Assignee: Myrna van Lunteren (was: Kathey Marsden)
Marking resolved, as the variable part of the test has been disabled.
> On IBM 1.7 TestDurabilityProperty fails with FAIL --
> derby.system.durability=test mode seems to be broken.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5865
> URL: https://issues.apache.org/jira/browse/DERBY-5865
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.10.1.1
> Environment: Linux trunk version: 10.10.0.0 alpha - (1362738)
> Reporter: Kathey Marsden
> Assignee: Myrna van Lunteren
> Labels: derby_triage10_10
> Fix For: 10.10.1.3, 10.11.0.0
>
>
> I saw this failure on IBM 1.7 on 7/17/2012
> http://people.apache.org/~myrnavl/derby_test_results/main/linux/testlog/ibm17/1362738-derbyall_diff.txt
> ********* Diff file derbyall/storeall/storemore/TestDurabilityProperty.diff
> *** Start: TestDurabilityProperty jdk1.7.0 storeall:storemore 2012-07-18
> 01:45:06 ***
> 1a2,5
> > FAIL -- derby.system.durability=test mode seems to be broken.
> > -- In this mode one would expect that inserts with autocommit off and on
> > would be in the same range as syncs are not happening but the difference
> > here seems to be more than the approximate estimated range.
> > -- Also comparing the time taken to do the inserts without this property
> > set seems to be in the same range as with this property set.
> > -- Please note this test times inserts and approximate estimates were
> > considered to report this observation.
> Test Failed.
> *** End: TestDurabilityProperty jdk1.7.0 storeall:storemore 2012-07-18
> 01:46:39 ***
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
