Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-672

Errors in Bamboo build after upgrading from Clover 2.4.0 to 2.5.1

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Medium Medium
    • won't fix
    • 2.5.1
    • None
    • None

      One of my modules with (luckily) only a few unit tests started giving this error on every unit test:

      java.lang.NoSuchFieldError: E
      at com.vcommerce.storefront.rightnow.RightNowLocatorTester.setUp(RightNowLocatorTester.java:19)

      The line number appears to always be the Junit setUp() method.

      In addition, two unit tests in the same test case throw this:

      java.lang.NoSuchMethodError: com_cenqua_clover.CoverageRecorder.globalSliceStart(Ljava/lang/Class;I)V
      at com.vcommerce.storefront.integrations.webloyalty.WLEncryptionTester.testEncryption(WLEncryptionTester.java:20)

      I can't find any differences between this module's build.xml and the other 10 that work fine. The only modification I've made to the build.xml along with the upgrade was to add:

      <taskdef resource="cloverjunitlib.xml" classpath="${clover.jar}"/>

      ... as recommended for Ant 1.7.

            [CLOV-672] Errors in Bamboo build after upgrading from Clover 2.4.0 to 2.5.1

            Owen made changes -
            Workflow Original: New Clover Workflow [ 897549 ] New: New Clover Workflow - Restricted [ 1474281 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 895130 ] New: New Clover Workflow [ 897549 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 180604 ] New: Clover Workflow [ 895130 ]
            Marek Parfianowicz made changes -
            Fix Version/s New: won't fix [ 38394 ]
            SlawekA (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            It seems to have been resolved long time ago, closing.

            SlawekA (Inactive) added a comment - It seems to have been resolved long time ago, closing.

            Cott Lang added a comment -

            Ha - I can relate to telecommuting, I too work completely remotely and end up staying up all night.

            I actually opened a new ticket in order to give someone else the opportunity to step up.

            You were correct, one of my build files had a very old flaw that didn't properly clean a directory. That resolved this entirely. I'll post my (hopefully) last problem in the original ticket.

            Thanks!

            Cott Lang added a comment - Ha - I can relate to telecommuting, I too work completely remotely and end up staying up all night. I actually opened a new ticket in order to give someone else the opportunity to step up. You were correct, one of my build files had a very old flaw that didn't properly clean a directory. That resolved this entirely. I'll post my (hopefully) last problem in the original ticket. Thanks!

            Yes, I should be The price of working on the other side of the world to your team!

            It also does apply to the NoSuchFieldError E.

            Michael Studman (Inactive) added a comment - Yes, I should be The price of working on the other side of the world to your team! It also does apply to the NoSuchFieldError E.

            Cott Lang added a comment -

            Shouldn't you be asleep?

            Does that apply to the "NoSuchFieldError: E" as well, or just the NoSuchMethodError?

            I'll keep digging, but that was my first suspicion and I'll be damned if I can find either an old version of Clover or any old jars.

            Cott Lang added a comment - Shouldn't you be asleep? Does that apply to the "NoSuchFieldError: E" as well, or just the NoSuchMethodError? I'll keep digging, but that was my first suspicion and I'll be damned if I can find either an old version of Clover or any old jars.

            Just FYI, jira.atlassian.com is not a proper support channel in that our effort to monitor problems is best effort but no guarantees. We have strict SLAs for issues raised on support.atlassian.com, however, and that is probably the best place to log these sorts of issues if you want a consistently quick response (I happen to have been JIRA wrangling tonight hence why I'm monitoring this area so closely).

            Michael Studman (Inactive) added a comment - Just FYI, jira.atlassian.com is not a proper support channel in that our effort to monitor problems is best effort but no guarantees. We have strict SLAs for issues raised on support.atlassian.com, however, and that is probably the best place to log these sorts of issues if you want a consistently quick response (I happen to have been JIRA wrangling tonight hence why I'm monitoring this area so closely).

              Unassigned Unassigned
              bccbd399478a Cott Lang
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: