db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5865) On IBM 1.7 TestDurabilityProperty fails with FAIL -- derby.system.durability=test mode seems to be broken.
Date Fri, 06 Dec 2013 00:52:35 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840754#comment-13840754
] 

Myrna van Lunteren commented on DERBY-5865:
-------------------------------------------

I have been able to see this test fail 8 times out of 100 with ibm 1.7 SR6 when I run with
specific JVM settings:
IBM_JAVA_OPTIONS=-Xcompressedrefs -Xgcpolicy:balanced -Xnoquickstart -Xjit

The output of one of these runs is:
1. With derby.system.durability=test,Test to see if syncs are not happening
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.
timeCommitOn = 2245
timeWithTestModeCommitOn = 3417
timeWithTestModeCommitOff = 443
Is warning message about derby.system.durability=test present in derby.log =true
log.ctrl file has durability testMode no sync marker value = true
2. shutdown database and reboot database without derby.system.durability=test and test for
marker in log.ctrl file
log.ctrl file has durability testMode no sync marker value = true
Is warning message about derby.system.durability=test present in derby.log =true

I am wondering if this is because there might be a time difference between the first run,
when the JIT hasn't kicked in yet, and subsequent runs. I'll play with modifying the test
to do one untimed insert before the 500 timed ones.

> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message