• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.0.2
    • 2.0.1
    • None
    • None

      Clover 2 is generating an OOM while writing reports for a large build. The build output is:


      26-Oct-2007 03:13:12 clover-guard:
      26-Oct-2007 03:13:12 [javac] WARNING: The <testresults> element is deprecated. It will be ignored.
      26-Oct-2007 03:13:12 [javac] WARNING: The <testresults> element is deprecated. It will be ignored.
      26-Oct-2007 03:13:12 [javac] WARNING: The <testresults> element is deprecated. It will be ignored.
      26-Oct-2007 03:13:12 [clover-report] Clover Version 2.0.1, built on October 19 2007
      26-Oct-2007 03:13:12 [clover-report] Loaded from: /n/​bin/​ant/​apache-ant-1.6.5/​lib/​clover.jar
      26-Oct-2007 03:13:12 [clover-report] Clover: Open Source License registered to Limewire.
      26-Oct-2007 03:13:12 [clover-report] Loading coverage database from: '/n/​bin/​bamboo/​data/​xml-data/​build-dir/​LW-NIGHTLY/​limewire/​clover/​clover.db'
      26-Oct-2007 03:14:55 [clover-report] Writing report to '/n/​bin/​bamboo/​data/​xml-data/​build-dir/​LW-NIGHTLY/​limewire/​clover/​html'
      26-Oct-2007 03:17:06
      26-Oct-2007 03:17:06 BUILD FAILED
      26-Oct-2007 03:17:06 java.lang.OutOfMemoryError: Java heap space

      (You can ignore the ​ character – that's just Bamboo adding a character that doesn't display on IE6.)

      I've attached the clover.db used for that build. You can reproduce the problem by checking out limewire with:
      cvs -d:pserver:guest@cvs.limewire.org:/cvs login
      type guest for the password
      cvs -d:pserver:guest@cvs.limewire.org:/cvs checkout limewire

      Then create a clover subdirectory within 'limewire', copy the clover.db into there. From the limewire directory, type: ant with.clover clover2html

        1. clover.db
          2.67 MB

            [CLOV-84] OOM Writing Reports

            Nick added a comment -

            Nick added a comment - This issue is replace by: http://support.atlassian.com/browse/CLV-4667

            Nick added a comment -

            No problem, Sam. Tests ran overnight, they took about 164 minutes to run. I'm going to close this case, and have created you a support case over at: http://support.atlassian.com/browse/CLV-4667 . Please let me know if you have problems viewing that issue.

            Best Regards,
            Nick

            Nick added a comment - No problem, Sam. Tests ran overnight, they took about 164 minutes to run. I'm going to close this case, and have created you a support case over at: http://support.atlassian.com/browse/CLV-4667 . Please let me know if you have problems viewing that issue. Best Regards, Nick

            Sam Berlin added a comment -

            All right – sorry about the posting in the wrong place. Good luck running the [incredibly long] tests. Don't be dismayed by the lots of failures!

            Sam Berlin added a comment - All right – sorry about the posting in the wrong place. Good luck running the [incredibly long] tests. Don't be dismayed by the lots of failures!

            Nick added a comment -

            Hi Sam,

            I'm currently running test-all since I need the coverage recording files to generate a clover report.

            Also, sorry this JIRA went so long unanswered, it did not appear on my radar as it was not assigned to the release I was working on.
            FYI - http://support.atlassian.com would be more appropriate for this kind of request as we have a support team monitoring that instance of JIRA constantly.

            Cheers and I hope I can give you some more news re your OOME soon.

            Cheers,
            Nick

            Nick added a comment - Hi Sam, I'm currently running test-all since I need the coverage recording files to generate a clover report. Also, sorry this JIRA went so long unanswered, it did not appear on my radar as it was not assigned to the release I was working on. FYI - http://support.atlassian.com would be more appropriate for this kind of request as we have a support team monitoring that instance of JIRA constantly. Cheers and I hope I can give you some more news re your OOME soon. Cheers, Nick

              npellow Nick
              392fb6eb772b Sam Berlin
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: