Derby
  1. Derby
  2. 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

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.3.1.4
    • Fix Version/s: 10.6.1.0
    • Component/s: Test
    • Labels:
      None
    • Environment:
      IBM iseries machine, ibm

      Description

      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.

        Issue Links

          Activity

          Myrna van Lunteren created issue -
          Myrna van Lunteren made changes -
          Field Original Value New Value
          Link This issue relates to DERBY-2948 [ DERBY-2948 ]
          Hide
          Myrna van Lunteren added a comment -

          Linking to two issues of derbynet/testconnection failing that show apparent diffs because of messages generated by the jvm.

          Show
          Myrna van Lunteren added a comment - Linking to two issues of derbynet/testconnection failing that show apparent diffs because of messages generated by the jvm.
          Myrna van Lunteren made changes -
          Link This issue relates to DERBY-3263 [ DERBY-3263 ]
          Myrna van Lunteren made changes -
          Link This issue incorporates DERBY-3273 [ DERBY-3273 ]
          Hide
          Myrna van Lunteren added a comment -

          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.

          Show
          Myrna van Lunteren added a comment - 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.
          Myrna van Lunteren made changes -
          Link This issue is related to DERBY-5084 [ DERBY-5084 ]
          Hide
          Myrna van Lunteren added a comment -

          Looks like I meant to close this for 10.6.

          Show
          Myrna van Lunteren added a comment - Looks like I meant to close this for 10.6.
          Myrna van Lunteren made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Fix Version/s 10.6.1.0 [ 12313727 ]
          Resolution Fixed [ 1 ]
          Gavin made changes -
          Workflow jira [ 12413786 ] Default workflow, editable Closed status [ 12797754 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Closed Closed
          1252d 17h 26m 1 Myrna van Lunteren 02/Mar/11 17:20

            People

            • Assignee:
              Unassigned
              Reporter:
              Myrna van Lunteren
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development