[
https://issues.apache.org/jira/browse/DERBY-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748577#action_12748577
]
Myrna van Lunteren commented on DERBY-4347:
-------------------------------------------
Although I'm wary of adding configurable properties (because the old test
harness had many, most of them badly documented and/or not working properly)
this one has long been on my wish list.
For instance, when running platform tests, for which I only have slower
machines available. Or, like Kathey says, for doing experiments with jvm
settings.
You can make a specialized build with the slower setting, but it gets old,
making the same change repeatedly.
I don't think making that change permanently for these one-off situations is
necessary.
There are a few tests which expect the server to fail, and those would be
sitting around even longer (although it's probably only 1 or 2 tests, so on a
complete testrun it probably doesn't matter so much). Also, I'd worry that we
hide server startup performance creep if we'd increase the default (although
there's probably/hopefully a performance tests for that somewhere).
I agree on Knut's point re the seconds vs. milliseconds.
> Provide a property to increase network server start timeout for JUnit tests
> -----------------------------------------------------------------------------
>
> Key: DERBY-4347
> URL: https://issues.apache.org/jira/browse/DERBY-4347
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.3.0, 10.6.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> Sometimes when running JUnit tests with jvm options that are known to slow
> things down significantly network server start timeouts can occur e.g.
> SecureServerTest( Opened = false, Authenticated= false,
> CustomDerbyProperties= null, WildCardHost= null
> )junit.framework.AssertionFailedError: Timed out waiting for network server
> to start:Spawned SpawnedNetworkServer exitCode=143
> at
> org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:203)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> The current wait time is 40 seconds and is set in
> org.apache.derbyTesting.junit.NetworkServerTestSetup
>
> /** Setting maximum wait time to 40 seconds. On some platforms
> * it may take this long to start the server. Increasing the wait
> * time should not adversely affect those
> * systems with fast port turnaround as the actual code loops for
> * SLEEP_TIME intervals, so should never see WAIT_TIME.
> */
> private static final long WAIT_TIME = 40000;
>
> It would be nice to have system property (maybe
> derby.tests.networkServerStartTimeout=<ms>) to allow this to be configurable
> in environments where we expect the start to take longer.
> I am not sure if there are other timeouts in the tests for replication etc or
> if they all use this same setting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
