[
https://issues.apache.org/jira/browse/DERBY-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724174#comment-13724174
]
Mike Matrigali commented on DERBY-5865:
---------------------------------------
I agree kathey that this test is likely not appropriate in the environment you
describe. Rather than patch on a patch, is there anyway you could
just disable this test in this environment. The defaults seem to be working
for most everyone else. It is likely that this test will continue to fail
in cases where hardware and jvm assumptions don't match the "usual". If this
test passes under any other jvm flags it is likely that other failure
is a test issue and not an actual bug.
It may help to add reporting the values of the interesting variables in the
message to be clear what is going on.
I have not looked at full test, but wonder if the base run might be affected by
the JIT flags but not subsequent runs. If so maybe changing the test
to run once and throw away that result to "warm up the JIT" might help. For
default JIT setting probably does not matter, but for wierd JIT testing
situations maybe.
> 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: Kathey Marsden
> Labels: derby_triage10_10
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
