I've submitted a Jira for the issue: https://issues.apache.org/jira/browse/AMQ-6177
I'll put together a patch over the weekend :) On Fri, Feb 19, 2016 at 8:23 PM, Jamie G. <[email protected]> wrote: > HA! > > Running org.apache.activemq.broker.scheduler.CronParserTest > > Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.107 > sec - in org.apache.activemq.broker.scheduler.CronParserTest > > > Changed my timezone from NST to EST. > > Cheers, > Jamie > > On Fri, Feb 19, 2016 at 8:20 PM, Jamie G. <[email protected]> wrote: >> I wonder if I change my timezone if they test would pass... >> Let me check :) >> >> On Fri, Feb 19, 2016 at 7:52 PM, artnaseef <[email protected]> wrote: >>> I wonder if it's timezone-related. There's odd logic in the test looking >>> for >>> 8:50, based on the snippet Jamie posted. >>> >>> Oddly it's using 20 minutes into the epoch as the time, and then somehow >>> expecting a different result if that returns 8 and 50 as follows: >>> >>> if (startHours == 8 && startMinutes == 50) { >>> >>> >>> >>> -- >>> View this message in context: >>> http://activemq.2283324.n4.nabble.com/Building-AMQ-5-13-1-from-tag-tp4707866p4707888.html >>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
