db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Cordes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1789) 'FAIL -- derby.system.durability=test mode seems to be broken.' in store/TestDurabilityProperty.java
Date Tue, 05 Dec 2006 08:52:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1789?page=comments#action_12455548 ] 
Stefan Cordes commented on DERBY-1789:

Time differences above are not caused by derby.system.durability=test but by different CPU
assignment between Eclipse 3.1.2 and the running program when in debug mode. Details follow

> 'FAIL -- derby.system.durability=test mode seems to be broken.' in store/TestDurabilityProperty.java
> ----------------------------------------------------------------------------------------------------
>                 Key: DERBY-1789
>                 URL: http://issues.apache.org/jira/browse/DERBY-1789
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions:
>         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/

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message