[
https://issues.apache.org/jira/browse/DERBY-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg closed DERBY-1789.
------------------------------
Resolution: Cannot Reproduce
Closing as "Cannot Reproduce" as this has not been seen in a long time.
> '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: Regression Test Failure
> 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.
-
You can reply to this email to add a comment to the issue online.
