[DERBY-1789] 'FAIL -- derby.system.durability=test mode seems to be broken.' in store/TestDurabilityProperty.java

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 10.2.1.6
• Component/s: Test
• 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
• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: Ole Solberg
• Created: 31/Aug/06 10:05
• Updated: 25/Sep/12 16:33
• Resolved: 24/Nov/08 08:16

Description

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

Issue Links

• duplicates: DERBY-5865 On IBM 1.7 TestDurabilityProperty fails with FAIL -- derby.system.durability=test mode seems to be broken.

Sub-Tasks

• Debugging Derby 10.2.1.6 applications with Eclipse 3.1.2 is 10 times slower than debugging 10.1.2.2 applications: Closed