[
https://issues.apache.org/jira/browse/DERBY-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622850#action_12622850
]
Ole Solberg commented on DERBY-1902:
------------------------------------
A slightly different signature has occurred on the 10.4 branch, Linux
2.6.18-53.1.14.el5, Sun Jvm 1.6
since 2008-07-04 / 674085.
See e.g.:
http://dbtg.thresher.com/derby/test/10.4Branch/jvm1.6/testing/testlog/lin/685954-derbyall_diff.txt
> Intermittent failures in predicatePushdown.sql
> ----------------------------------------------
>
> Key: DERBY-1902
> URL: https://issues.apache.org/jira/browse/DERBY-1902
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, SQL, Test
> Affects Versions: 10.3.1.4
> Environment: Seen on both Solaris 10 and Linux on 2-CPU Opteron
> boxes, disk cache off
> Reporter: Øystein Grøvlen
> 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.
-
You can reply to this email to add a comment to the issue online.
