[
https://issues.apache.org/jira/browse/DERBY-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399081#comment-13399081
]
Mamta A. Satoor commented on DERBY-1789:
----------------------------------------
This test failed on one of the Linux/VMware machine running top of the trunk
10.10.0.0 alpha - (1352388) with ibm17. The failure is as follows
Failure Details:
********* Diff file derbyall/storeall/storemore/TestDurabilityProperty.diff
*** Start: TestDurabilityProperty jdk1.7.0 storeall:storemore 2012-06-21
00:59:44 ***
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-06-21
01:00:37 ***
Java version - JRE 1.7.0 IBM J9 2.6 Linux x86-32 20110810_88604 (JIT enabled,
AOT enabled)
> 'FAIL -- derby.system.durability=test mode seems to be broken.' in
> store/TestDurabilityProperty.java
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1789
> URL: https://issues.apache.org/jira/browse/DERBY-1789
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.2.1.6
> Environment: Host: 2 X i86pc i386 (AMD Opteron(tm) Processor 250):
> 2388 MHz, unknown cache. 2048 Megabytes Total Memory.
> OS: Solaris Nevada snv_43 X86 64 bits - SunOS 5.11 snv_43
> JVM: Sun Microsystems Inc. 1.4.2_05
> Reporter: Ole Solberg
> Priority: Minor
>
> Diff says:
> "> 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.
> "
> Could this be caused by other high load on the machine? Not that I can
> confirm that this happended here though.
> Log:
> http://www.multinet.no/~solberg/public/Apache/10.2.1.1_RC/jvm1.4/testlog/solN+1/436991-derbyall_diff.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
