Derby
  1. Derby
  2. DERBY-4429

Let StressMultiTest read Threads and Minutes to run as system property

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: 10.6.1.0
    • Component/s: Test
    • Labels:
      None
    • Environment:
      All

      Description

      Allow StressMultiTest to read System Property "derby.tests.ThreadsMinutes" to set the number of threads and minutes testStressMulti should run.
      Example: '-Dderby.tests.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.tests.ThreadsMinutes=33x3' and
      increase the load for a specific test: '-Dderby.tests.ThreadsMinutes=200x60'.
      The StressMultiTest defaults are as set with '-Dderby.tests.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.

      1. DERBY-StressMultiOptions_stat_2.txt
        0.1 kB
        Ole Solberg
      2. DERBY-StressMultiOptions_diff_2.txt
        2 kB
        Ole Solberg
      3. DERBY-StressMultiOptions_stat.txt
        0.1 kB
        Ole Solberg
      4. DERBY-StressMultiOptions_diff.txt
        1 kB
        Ole Solberg

        Activity

        Hide
        Ole Solberg added a comment -

        Committed DERBY-StressMultiOptions_diff_2 to trunk as revision 832364.

        Show
        Ole Solberg added a comment - Committed DERBY-StressMultiOptions_diff_2 to trunk as revision 832364.
        Hide
        Ole Solberg added a comment -

        Uploading a new patch DERBY-StressMultiOptions_diff_2. that uses
        "derby.tests.ThreadsMinutes"
        and
        gives an 'alarm' if parsing the input fails.

        Running tests now.

        Show
        Ole Solberg added a comment - Uploading a new patch DERBY-StressMultiOptions_diff_2. that uses "derby.tests.ThreadsMinutes" and gives an 'alarm' if parsing the input fails. Running tests now.
        Hide
        Ole Solberg added a comment -

        Thanks for catching that Kristian! It should be "derby.tests.ThreadsMinutes". My "typo"....

        I'll upload a new patch.

        Show
        Ole Solberg added a comment - Thanks for catching that Kristian! It should be "derby.tests.ThreadsMinutes". My "typo".... I'll upload a new patch.
        Hide
        Kristian Waagan added a comment -

        Hi Ole,

        I note that other tests use "derby.tests." instead of "derby.test.". Maybe it would be better to agree on a common prefix?
        I was also surprised that I didn't get any error messages when I specified derby.tests.debug=true, but I did get a message when I specified derby.tests.trace=true. It is possible that I have misunderstood the meaning of these properties.
        Maybe a warning message should be printed regardless of the values for debug and trace if parsing the input fails?

        +1 to commit if the prefix of the property is aligned with the existing one

        Show
        Kristian Waagan added a comment - Hi Ole, I note that other tests use "derby.tests." instead of "derby.test.". Maybe it would be better to agree on a common prefix? I was also surprised that I didn't get any error messages when I specified derby.tests.debug=true, but I did get a message when I specified derby.tests.trace=true. It is possible that I have misunderstood the meaning of these properties. Maybe a warning message should be printed regardless of the values for debug and trace if parsing the input fails? +1 to commit if the prefix of the property is aligned with the existing one

          People

          • Assignee:
            Ole Solberg
            Reporter:
            Ole Solberg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development