db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1789) 'FAIL -- derby.system.durability=test mode seems to be broken.' in store/TestDurabilityProperty.java
Date Fri, 08 Sep 2006 23:34:24 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1789?page=comments#action_12433528 ] 
            
Sunitha Kambhampati commented on DERBY-1789:
--------------------------------------------

>Could this be caused by other high load on the machine? Not that I can confirm that this
happended here though. 

Yes.  This is more of a performance test. This test uses an approximation to test whether
the inserts went faster with this property enabled versus when it is not enabled.  

I briefly looked at the report at http://www.multinet.no/~solberg/public/Apache/#TenTwoZeroSnapshots
and I dont see this test failing there.  (btw -  Very helpful summary report. - Thanks for
the great work, Ole.).

If  you can confirm this test is not failing, then it may be ok to close this issue.  Thanks.


> '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: 10.2.1.0
>         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 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

        

Mime
View raw message