[
https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772531#action_12772531
]
Ole Solberg commented on DERBY-4429:
------------------------------------
Thanks for catching that Kristian! It should be "derby.tests.ThreadsMinutes".
My "typo"....
I'll upload a new patch.
> Let StressMultiTest read Threads and Minutes to run as system property
> ----------------------------------------------------------------------
>
> Key: DERBY-4429
> URL: https://issues.apache.org/jira/browse/DERBY-4429
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: DERBY-StressMultiOptions_diff.txt,
> DERBY-StressMultiOptions_stat.txt
>
>
> Allow StressMultiTest to read System Property "derby.test.ThreadsMinutes" to
> set the number of threads and minutes testStressMulti should run.
> Example: '-Dderby.test.ThreadsMinutes=33x3'.
> This will set
> StressMultiTest.THREADS to 33 and
> StressMultiTest.MINUTES to 3.
> This can be utilized to for example
> reduce the time StressMultiTest is run in a tinderbox test:
> '-Dderby.test.ThreadsMinutes=33x3' and
> increase the load for a specific test: '-Dderby.test.ThreadsMinutes=200x60'.
> The StressMultiTest defaults are as set with
> '-Dderby.test.ThreadsMinutes=10x10'.
> By default the test suite for StressMultiTest is set to run in embedded,
> client and encryption mode, i.e. 3 x the Minutes specified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
