Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.4, 2.2.0-beta-1
    • Component/s: None
    • Labels:
      None

      Description

      With gradle 1.4/1.5 the Groovy now run a lot of faster, but i noticed that some test take a lot of the total time.

      The main "offenders" seem to be:

      org.codehaus.groovy.reflection.WeakMapTest.testClassUnload takes 25% of the total test execution time (over 2 minutes on the buildserver). Is it really necessary to execute the loop a 1000 times or would a fewer loops /fewer gc calls suffice?

      groovy.transform.stc.MiscSTCTest.testFibonacci takes 46 seconds and looks more like a "manual" performance test (no asserts concerning performance). Can this test be deactivated (or at least calculate the fibonacci function of a smaller number)?

      org.codehaus.groovy.classgen.asm.sc.MiscStaticCompileTest.testEachFileRecurse can also be slow. It takes 22 seconds on the buildserver at the moment. I guess for this test it would be enough to create a some temp directories with files in them instead of iterating over the whole java.io.tmpdir?

        Attachments

          Activity

            People

            • Assignee:
              pschumacher Pascal Schumacher
              Reporter:
              pschumacher Pascal Schumacher
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: