db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3089) convert tests that cause failures because of jvm based messages to junit, or adjust old test harness files, for test failures during iseries run
Date Tue, 09 Jun 2009 22:08:07 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717839#action_12717839
] 

Myrna van Lunteren commented on DERBY-3089:
-------------------------------------------

I'm marking this fixed in 10.6...
1. - the workaround works ok. I run derbyrunjartest and 1 network server test.
I've not seen a failure in tools/ijConnName in recent runs, so I don't think there's a need
anymore to fix up the sed-ing. Eventually the test ought to get run through a sqlscripts junit
test.
3. and 4 were converted and have not failed in recent runs.

> convert tests that cause failures because of jvm based messages to junit, or adjust old
test harness files, for test failures during iseries run
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3089
>                 URL: https://issues.apache.org/jira/browse/DERBY-3089
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.1.4
>         Environment: IBM iseries machine, ibm 
>            Reporter: Myrna van Lunteren
>
> A number of derbyall tests failed on a recent run on an ibm iseries machine. The test
failures were as follows:
> 1. each time a session connects to a jar file for the first time, a message is printed
(e.g. 'Attaching to /home/MYRNA/jars/derbyclient.jar'). This results in some diffs.
>     The solution would be to devise a pattern for each jar file & add that to the
delete line in harness/Sed.java.  A workaround would be to run a selection of troublesome
tests (metadata.java, derbyrun.jar, metadata.java with DerbyNetClient) before attempting derbyall.
> 2. tools/ijConnName.sql fails because the line 'ERROR 08001 - No suitable driver' pops
up in a different location. This is probably on a slow machine. A solution would be to remove
the line from this test's master altogether by adding a ijConnName_sed.properties file.
> 3.  derbynet/testconnection.java fails because the jvm generated message is a little
different, instead of:
> 		< Could not connect to Derby Network Server on host xxxFILTERED_HOSTNAMExxx - port
9393: Connection refused ...
> 	we get more text: 
> 		> Could not connect to Derby Network Server on host xxxFILTERED_HOSTNAMExxx, port
9393: A remote host refused an attempted connect operation.
> 	Solution would be to add more filtering to the testconnection_sed.properties file.
> 4. derbynet/NSinSameJVM fails because of different jvm generated strings for the main
thread. 
> 		expected: main-NSinSameJVM: Derby drivers loaded
> 		iseries:   Thread-0-NSinSameJVM: Derby drivers loaded 
>      Solution would be to add masking of this difference to the NSinSameJVM_sed.properties
file.
> If these tests could get converted to junit that would be preferable to fixing up masters.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message