Thanks All. I was little concerned that I broke the build in my very first patch :)
Regards On Tue, May 5, 2015 at 3:43 PM, Rajat Khandelwal <[email protected]> wrote: > This is not because of your patch. Existing bug in TimePartition class. > Specifically for Update Period Quarterly. It was missed earlier because all > the test cases were written in April(1st month of the quarter) :D. > > Don't worry about it, it will be fixed in a short while. I already have a > fix. > > On Tue, May 5, 2015 at 12:39 PM Arshad Matin <[email protected]> > wrote: > > > It is failing for us also. There is a JIRA raised for the same > > JIRA : https://issues.apache.org/jira/browse/LENS-534 > > > > On Tue, May 5, 2015 at 12:00 PM, Yash Sharma <[email protected]> wrote: > > > > > Hi All, > > > Is anyone else stumbling across this failure. I see this has been > > > introduced yesterday after my patch merged in. > > > > > > I would like to help on this if my patch caused this someway. > > > > > > Thanks, > > > > > > testTimeRange(org.apache.lens.cube.metadata.TestTimePartition) Time > > > elapsed: 0.005 sec <<< FAILURE! > > > java.lang.AssertionError: expected [10] but found [9] > > > at org.testng.Assert.fail(Assert.java:94) > > > at org.testng.Assert.failNotEquals(Assert.java:494) > > > at org.testng.Assert.assertEquals(Assert.java:123) > > > at org.testng.Assert.assertEquals(Assert.java:265) > > > at org.testng.Assert.assertEquals(Assert.java:275) > > > at > > > > > > > > > org.apache.lens.cube.metadata.TestTimePartition.testTimeRange(TestTimePartition.java:112) > > > > > > > -- > > _____________________________________________________________ > > The information contained in this communication is intended solely for > the > > use of the individual or entity to whom it is addressed and others > > authorized to receive it. It may contain confidential or legally > privileged > > information. If you are not the intended recipient you are hereby > notified > > that any disclosure, copying, distribution or taking any action in > reliance > > on the contents of this information is strictly prohibited and may be > > unlawful. If you have received this communication in error, please notify > > us immediately by responding to this email and then delete it from your > > system. The firm is neither liable for the proper and complete > transmission > > of the information contained in this communication nor for any delay in > its > > receipt. > > >
