You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Øystein Grøvlen (JIRA)" <de...@db.apache.org> on 2006/10/02 15:16:04 UTC

[jira] Commented: (DERBY-1902) Intermittent failures in predicatePushdown.sql

    [ http://issues.apache.org/jira/browse/DERBY-1902?page=comments#action_12439136 ] 
            
Øystein Grøvlen commented on DERBY-1902:
----------------------------------------

The failure was first observed in the nightly run on svn revision 449444.  It was not observed on 448277.  However, the failure is intermittent so one cannot be sure that it was introduced between those revisions.

> 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