Derby
  1. Derby
  2. DERBY-1789

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

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: None
    • Component/s: Test
    • Labels:
      None
    • 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

      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

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Ole Solberg
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development