I've copied what i'm seeing into a gist file: https://gist.github.com/anonymous/bc2becd86ec3ce3caf98
For the unit test to pass, the current value should be 3000000, yet on my platform i'm seeing Current == 1200000. Still looking into why this is occurring for me... On Fri, Feb 19, 2016 at 2:18 PM, Jamie G. <[email protected]> wrote: > Hi Tim, > > Thank you for the suggestion. > > Which version of Maven & Java are you using? > > Cheers, > Jamie > > On Fri, Feb 19, 2016 at 1:34 PM, Christopher Shannon > <[email protected]> wrote: >> You can use -fae so that it fails at the end and you can continue if that >> one test keeps breaking for you. >> >> On Fri, Feb 19, 2016 at 12:01 PM, Timothy Bish <[email protected]> wrote: >> >>> On 02/19/2016 11:59 AM, Jamie G. wrote: >>> > OK, >>> > >>> > Was there any special maven invocation? I'm just using mvn clean install. >>> >>> same here, didn't do anything special, tried on another box and passes >>> there as well. >>> >>> > >>> > On Fri, Feb 19, 2016 at 1:26 PM, Timothy Bish <[email protected]> >>> wrote: >>> >> On 02/19/2016 11:34 AM, Jamie G. wrote: >>> >>> Hi All, >>> >>> >>> >>> I'm attempting to building AMQ 5.13.1 from tag in order to test some >>> >>> changes I'm making for AMQ-6176. >>> >>> >>> >>> When i try to build AMQ 5.13.1 I see: >>> >>> >>> >>> Tests run: 15, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.104 >>> >>> sec <<< FAILURE! - in >>> >>> org.apache.activemq.broker.scheduler.CronParserTest >>> >>> >>> testgetNextTimeMinutes(org.apache.activemq.broker.scheduler.CronParserTest) >>> >>> Time elapsed: 0.004 sec <<< FAILURE! >>> >>> java.lang.AssertionError: expected:<600000> but was:<2400000> >>> >>> at org.junit.Assert.fail(Assert.java:88) >>> >>> at org.junit.Assert.failNotEquals(Assert.java:834) >>> >>> at org.junit.Assert.assertEquals(Assert.java:645) >>> >>> at org.junit.Assert.assertEquals(Assert.java:631) >>> >>> at >>> org.apache.activemq.broker.scheduler.CronParserTest.testgetNextTimeMinutes(CronParserTest.java:276) >>> >>> >>> >>> Results : >>> >>> >>> >>> Failed tests: >>> >>> CronParserTest.testgetNextTimeMinutes:276 expected:<600000> but >>> was:<2400000> >>> >>> >>> >>> [INFO] Reactor Summary: >>> >>> [INFO] >>> >>> [INFO] ActiveMQ ........................................... SUCCESS [ >>> 0.937 s] >>> >>> [INFO] ActiveMQ :: Openwire Generator ..................... SUCCESS [ >>> 1.140 s] >>> >>> [INFO] ActiveMQ :: Client ................................. FAILURE [ >>> 59.076 s] >>> >>> ... >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> [INFO] BUILD FAILURE >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> [INFO] Total time: 01:01 min >>> >>> [INFO] Finished at: 2016-02-19T12:25:54-03:30 >>> >>> [INFO] Final Memory: 56M/951M >>> >>> >>> >>> Here is my environment: >>> >>> Jamies-iMac:amq5131 jgoodyear$ mvn -version >>> >>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; >>> >>> 2015-11-10T13:11:47-03:30) >>> >>> Maven home: /x1/tools/apache-maven-3.3.9 >>> >>> Java version: 1.8.0_73, vendor: Oracle Corporation >>> >>> >>> >>> Is that test case expected to fail? >>> >>> >>> >>> Follow up question, if that test case is expected to fail, are there >>> >>> other tests I should expect to fail too? >>> >>> >>> >>> I'd like to be able to test my changes but is hard to when tag appears >>> >>> unstable :( >>> >>> >>> >>> Cheers, >>> >>> Jamie >>> >>> >>> >> Built that tag locally and the test is passing fine, also checked CI and >>> >> there doesn't seem to be any recent failures of that test. Might be >>> >> good to try and debug it a bit to see why it fails locally. >>> >> >>> >> -- >>> >> Tim Bish >>> >> twitter: @tabish121 >>> >> blog: http://timbish.blogspot.com/ >>> >> >>> >>> >>> -- >>> Tim Bish >>> twitter: @tabish121 >>> blog: http://timbish.blogspot.com/ >>> >>>
