Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6178

AutoloadTest does not proprogate original jvm -D flags to spawned JVM, leading to LAB regression test failures

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • High Value Fix
    • Regression Test Failure

    Description

      IBM lab nightly regression testing is seeing numerious intermittent errors while running the
      AutoloadTest. This regression testing often runs multiple runs of Suites.all on the same machine at
      the same time and uses the -Dderby.tests.basePort=3500 option to the tests to insure network
      server is created on different ports and don't intefere.

      I think the following code in this test that spawn a process is not going pass that port info onto the network
      server startup and then lead to problems:

      /**

      • Run {@code AutoloadTest}

        in a separate JVM.
        */
        public void spawnProcess() throws Exception {
        String[] cmd =

        { "junit.textui.TestRunner", spawnedTestClass.getName() }

        ;

      SpawnedProcess proc =
      new SpawnedProcess(execJavaCmd(cmd), spawnedTestClass.getName());

      if (proc.complete() != 0)

      { fail(proc.getFailMessage("Test process failed")); }

      }

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mikem Mike Matrigali
            mikem Mike Matrigali
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment