db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1902) Intermittent failures in predicatePushdown.sql
Date Fri, 29 Sep 2006 15:18:50 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1902?page=comments#action_12438729 ] 
            
A B commented on DERBY-1902:
----------------------------

Is it possible to post the files for the run when it fails?  And do you have the svn number
for the first time this failure was seen?

Interesting observation about the disk cache--thanks for bringing that up.  Is it feasible
to turn disk cache on for one of the machines that's failing and run the tests for a couple
of days to see if that makes a difference?  Thanks Øystein...

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