[ https://issues.apache.org/jira/browse/DERBY-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577725#action_12577725 ]
Jørgen Løland commented on DERBY-1902: -------------------------------------- I saw this on Solaris 10/x86 on revision 635860: *** Start: predicatePushdown jdk1.5.0_06 derbyall:derbylang 2008-03-11 15:34:04 *** 4639 del < Hash Join ResultSet: 4639a4639 > Nested Loop Join ResultSet: 4718 del < Hash Table ResultSet (11): 4718a4718 > Sort ResultSet: 4720 del < Hash table size = 100 4721 del < Hash key is column number 0 4722 del < Rows seen = 104 4723 del < Rows filtered = 0 ... and so on. I have the entire test directory intact if requested. > 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.