[ http://issues.apache.org/jira/browse/DERBY-407?page=all ]
A B resolved DERBY-407:
-----------------------
Resolution: Fixed
The derby.optimizer.noTimeout workaround (as commited almost a year ago) allows
this test to run without failure and seems like the appropriate fix (different
machines will optimize at different speeds, so it makes sense that optimizer
"timeout" could lead to different plans--the best way to avoid this is to
disable optimizer timeout, as is also done in other tests that print query
plans). So I'm marking this issue as resolved and closing it.
If anyone would like to do followup investigation at a later time, s/he should
feel free to file another Jira issue and proceed there.
> predicatesIntoViews test failure on slow machine in Derby 10.1 branch version
> 201931
> ------------------------------------------------------------------------------------
>
> Key: DERBY-407
> URL: http://issues.apache.org/jira/browse/DERBY-407
> Project: Derby
> Type: Test
> Components: Test
> Versions: 10.1.1.0
> Environment: Java Version: 1.4.2_04
> Java Vendor: Hewlett-Packard Company
> Java home: /usr/tandem/java/jre
> Java classpath:
> /home/john/j2ee/derbyTests/derby-10.1-branch/jars/derby.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbytools.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbynet.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyclient.jar:/home/john/j2ee/derbyTests/common-jars/db2jcc.jar:/home/john/j2ee/derbyTests/common-jars/db2jcc_license_c.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyTesting.jar:/home/john/j2ee/derbyTests/common-jars/jakarta-oro-2.0.8.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_de_DE.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_es.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_fr.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_it.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_ja_JP.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_ko_KR.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_pt_BR.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_zh_CN.jar:/home/john/j2ee/derbyTests/derby-10.1-branch/jars/derbyLocale_zh_TW.jar:/usr/tandem/java/lib/classes.zip:/usr/tandem/javaextv20/lib/tdmext.jar:/usr/tandem/jdbcMp/current/lib/sqlmp.jar:/usr/tandem/jdbcMx/current/lib/jdbcMx.jar:.
> OS name: NONSTOP_KERNEL
> OS architecture: mips
> OS version: G06
> Java user name: SUPER.JOHN
> Java user home: /home/john
> Java user dir: /home/john/j2ee/derbyTests/derby-10.1-branch/testOutput
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.4
> Reporter: John Sisson
> Attachments: derby407_workaround.patch, derbylang_report.txt
>
> The predicatesIntoViews test (part of the derbylang suite) fails when running
> the tests on a busy/slow system, but they pass when I run them on my fast
> Windows box.
> It appears that the failure could be due to different optimizations being
> performed due to the difference in speed of the machines. This needs to be
> confirmed that it is the case of the test failure. I will attach the test
> summary to this issue.
> I also noticed that the test report said 0% fail even though one test failed.
> All derbylang tests passed on Windows XP.
> Thanks,
> John
--
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
