db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-6178) AutoloadTest does not proprogate orignal jvm -D flags to spawned JVM, leading to LAB regression test failures
Date Fri, 12 Apr 2013 20:48:16 GMT
Mike Matrigali created DERBY-6178:
-------------------------------------

             Summary: AutoloadTest does not proprogate orignal jvm -D flags to spawned JVM,
leading to LAB regression test failures
                 Key: DERBY-6178
                 URL: https://issues.apache.org/jira/browse/DERBY-6178
             Project: Derby
          Issue Type: Bug
          Components: Test
    Affects Versions: 10.11.0.0
            Reporter: Mike Matrigali
            Priority: Critical


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"));
        }
    }


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message