Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-M1
    • Fix Version/s: 2.0 ITR7
    • Component/s: Transport: Quartz
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-786Move JournalPersistenceStrategy & tests into the sandbox since it is unreliable
      MULE-2208HTTPS Functional Test Case Unreliable
      MULE-7892Enable testing mode in functional tests
      MULE-8233Move tests/functional tests to tests/integration
      MULE-3201The Quartz endpoint schema needs some love
      MULE-8319Upgrade of quartz library to latest version
      MULE-7784Configure build for skipping functional tests
      MULE-9Functional tests for all providers
      MULE-1022Improvements to functional / integration tests
      MULE-1848Quartz legacy test failing in 2.0

      Description

      Quartz Functional Test is failing randomly (both in CI and on my machine); removing from tests for now.

      -------------------------------------------------------------------------------
      Test set: org.mule.providers.quartz.QuartzFunctionalTestCase
      -------------------------------------------------------------------------------
      Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.365 sec <<< FAILURE!
      mule receiver job (org.mule.providers.quartz.QuartzFunctionalTestCase) Time elapsed: 0.357 sec <<< FAILURE!
      junit.framework.AssertionFailedError: expected:<4> but was:<3>
      at junit.framework.Assert.fail(Assert.java:47)
      at junit.framework.Assert.failNotEquals(Assert.java:280)
      at junit.framework.Assert.assertEquals(Assert.java:64)
      at junit.framework.Assert.assertEquals(Assert.java:133)
      at junit.framework.Assert.assertEquals(Assert.java:139)
      at org.mule.providers.quartz.QuartzFunctionalTestCase.testMuleReceiverJob(QuartzFunctionalTestCase.java:31)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        Activity

        Hide
        andrew cooke added a comment -

        Just failed on bamboo with 2 instead of 4 (see above).

        Removing from build.

        Both Quartz Functional Tests are now excluded. Raising this to critical.

        Show
        andrew cooke added a comment - Just failed on bamboo with 2 instead of 4 (see above). Removing from build. Both Quartz Functional Tests are now excluded. Raising this to critical.
        Hide
        andrew cooke added a comment -

        Sorry, this was confused. In fact, the bamboo report is confused. Two different classes (Legacy and not) are mentioned. Investigating further.

        Show
        andrew cooke added a comment - Sorry, this was confused. In fact, the bamboo report is confused. Two different classes (Legacy and not) are mentioned. Investigating further.
        Hide
        andrew cooke added a comment -

        OK, so the bamboo "name" field is truncated. This is the org.mule.providers.quartz.QuartzFunctionalLegacyTestCase that is now failing and removed. Previously it was the org.mule.providers.quartz.QuartzFunctionalTestCase.

        The new stack trace is:
        expected:<4> but was:<2>
        junit.framework.AssertionFailedError: expected:&4& but was:&2&
        at junit.framework.Assert.fail(Assert.java:47)
        at junit.framework.Assert.failNotEquals(Assert.java:280)
        at junit.framework.Assert.assertEquals(Assert.java:64)
        at junit.framework.Assert.assertEquals(Assert.java:133)
        at junit.framework.Assert.assertEquals(Assert.java:139)
        at org.mule.providers.quartz.QuartzFunctionalLegacyTestCase.testMuleReceiverJob(QuartzFunctionalLegacyTestCase.java:31)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at junit.framework.TestCase.runTest(TestCase.java:164)
        at junit.framework.TestCase.runBare(TestCase.java:130)
        at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:206)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:120)
        at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:176)
        at junit.framework.TestSuite.runTest(TestSuite.java:230)
        at junit.framework.TestSuite.run(TestSuite.java:225)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
        at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
        at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
        at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
        at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
        at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)

        Show
        andrew cooke added a comment - OK, so the bamboo "name" field is truncated. This is the org.mule.providers.quartz.QuartzFunctionalLegacyTestCase that is now failing and removed. Previously it was the org.mule.providers.quartz.QuartzFunctionalTestCase. The new stack trace is: expected:<4> but was:<2> junit.framework.AssertionFailedError: expected:&4& but was:&2& at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:280) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:133) at junit.framework.Assert.assertEquals(Assert.java:139) at org.mule.providers.quartz.QuartzFunctionalLegacyTestCase.testMuleReceiverJob(QuartzFunctionalLegacyTestCase.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:206) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:176) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
        Hide
        andrew cooke added a comment -

        found one (working) test in integration, which is all i need for endpoint config work, so dropping this again (but will move test from integration into quartz, if possible).

        Show
        andrew cooke added a comment - found one (working) test in integration, which is all i need for endpoint config work, so dropping this again (but will move test from integration into quartz, if possible).
        Hide
        Dirk Olmes added a comment -

        QuartzFunctionalTestCase has been running without failures for quite some time now. Closing.

        Show
        Dirk Olmes added a comment - QuartzFunctionalTestCase has been running without failures for quite some time now. Closing.

          People

          • Assignee:
            Unassigned
            Reporter:
            andrew cooke
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development