Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <25013241.1159543130655.JavaMail.jira@brutus>
Date: Fri, 29 Sep 2006 08:18:50 -0700 (PDT)
From: "A B (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1902) Intermittent failures in
 predicatePushdown.sql
In-Reply-To: <12398301.1159523150038.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

    [ http://issues.apache.org/jira/browse/DERBY-1902?page=3Dcomments#actio=
n_12438729 ]=20
           =20
A B commented on DERBY-1902:
----------------------------

Is it possible to post the files for the run when it fails?  And do you hav=
e 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 failin=
g and run the tests for a couple of days to see if that makes a difference?=
  Thanks =C3=98ystein...

> 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 b=
oxes, disk cache off
>            Reporter: =C3=98ystein Gr=C3=B8vlen
>             Fix For: 10.3.0.0
>
>
> For the last week, there have been intermittent failures in the night tes=
t in lang/predicatePushdown.sql.  There is a plan diff which starts as foll=
ows:
> ********* Diff file derbyall/derbylang/predicatePushdown.diff
> *** Start: predicatePushdown jdk1.5.0_07 derbyall:derbylang 2006-09-29 00=
:39:36 ***
> 4593 del
> < =09=09=09Hash Join ResultSet:
> 4593a4593
> > =09=09=09Nested Loop Join ResultSet:
> I did not find any changes that seem relevant before the first failing ni=
ght test.
> This test has not failed in the tinderbox test which runs on a computer w=
ith the disk cache on.  For both computers where the failure is seen, the d=
isk cache has been turned off.  Hence, it may be that another plan is picke=
d because of slower I/O.

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