db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1902) Intermittent failures in predicatePushdown.sql
Date Thu, 05 Oct 2006 14:02:20 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1902?page=comments#action_12440142 ] 
            
Øystein Grøvlen commented on DERBY-1902:
----------------------------------------

I turned the disk cache back on the Solaris x86 box, and the test still fails.  (The test
duration became significantly shorter so I think the disk cache setting was really changed.)
 Hence, the disk cache seems not to be causing this.  It is strange that the tinderbox test
which run on a similar computer never experiences this failure.

> Intermittent failures in predicatePushdown.sql
> ----------------------------------------------
>
>                 Key: DERBY-1902
>                 URL: http://issues.apache.org/jira/browse/DERBY-1902
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL, Test, Regression Test Failure
>    Affects Versions: 10.3.0.0
>         Environment: Seen on both Solaris 10 and Linux on 2-CPU Opteron boxes, disk cache
off
>            Reporter: Øystein Grøvlen
>             Fix For: 10.3.0.0
>
>         Attachments: derbylang.zip
>
>
> For the last week, there have been intermittent failures in the night test in lang/predicatePushdown.sql.
 There is a plan diff which starts as follows:
> ********* Diff file derbyall/derbylang/predicatePushdown.diff
> *** Start: predicatePushdown jdk1.5.0_07 derbyall:derbylang 2006-09-29 00:39:36 ***
> 4593 del
> < 			Hash Join ResultSet:
> 4593a4593
> > 			Nested Loop Join ResultSet:
> I did not find any changes that seem relevant before the first failing night test.
> This test has not failed in the tinderbox test which runs on a computer with the disk
cache on.  For both computers where the failure is seen, the disk cache has been turned off.
 Hence, it may be that another plan is picked because of slower I/O.

-- 
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