Filed https://issues.apache.org/jira/browse/EAGLE-128
And PR https://github.com/apache/incubator-eagle/pull/64 for the fix Please help review On Fri, Jan 15, 2016 at 2:39 PM, Michael Wu <mchl....@gmail.com> wrote: > cool, thanks Edward and Ralph! > > On Fri, Jan 15, 2016 at 1:16 PM, Zhang, Edward (GDI Hadoop) < > yonzh...@ebay.com> wrote: > > > This is related to EAGLE-79, I think Ralph has said he will fix that. > > > > Thanks > > Edward > > > > On 1/13/16, 0:29, "Michael Wu" <mchl....@gmail.com> wrote: > > > > >Hi team, > > > > > >We're almost there, only 1 test case failed in the latest build: > > >https://builds.apache.org/job/incubator-eagle-main/12/testReport/, > please > > >try to tackle it! > > > > > >Thanks. > > >Michael > > > > > >On Tue, Jan 12, 2016 at 2:35 PM, Michael Wu <mchl....@gmail.com> wrote: > > > > > >> Okay, thanks. > > >> > > >> On Tue, Jan 12, 2016 at 12:22 PM, Zhang, Edward (GDI Hadoop) < > > >> yonzh...@ebay.com> wrote: > > >> > > >>> I have fixed > > >>> > > >>> > > > >>>org.apache.eagle.alert.state.TestSiddhiStateSnapshotAndRestore.persisten > > >>>ceT > > >>> est7, will create pull request. > > >>> > > >>> For https://github.com/apache/incubator-eagle/pull/43, can you look > at > > >>> why > > >>> it is not passing the checks. We need merge that pull request 43 > soon. > > >>> > > >>> Thanks > > >>> edward > > >>> > > >>> On 1/11/16, 19:05, "Michael Wu" <mchl....@gmail.com> wrote: > > >>> > > >>> >Hi all, > > >>> > > > >>> >I've setup a CI job for building and running unit test against > ealge's > > >>> >master branch, the job is at: > > >>> >https://builds.apache.org/job/incubator-eagle-main/, with unit test > > >>> >failing > > >>> >all the time. I think it's the time for us to reach out and fix the > > >>>unit > > >>> >tests. > > >>> > > > >>> >Each time the job fails, it's configured to send out an email to all > > >>>of > > >>> us > > >>> >with subject starting with "[EAGLE BUILD FAILED]", please take a > look > > >>> when > > >>> >you receive such emails to make sure if there is any failing case of > > >>>your > > >>> >own, or you can define a rule/label to classify them. > > >>> > > > >>> >For every CI build, there is a testing result page of it, on which > we > > >>>can > > >>> >see overall status of the build. > > >>> > > > >>> >To get to the test result page, we can either click into a specific > > >>>build > > >>> >then click "Test Result" in the left-nav, or use below url template > > >>>with > > >>> >replacing build-number and then open it in browsers: > > >>> > > > >>> > > >>> > > https://builds.apache.org/job/incubator-eagle-main/${build-number}/testR > > >>>ep > > >>> >ort/ > > >>> >. > > >>> > > > >>> >E.g. the 7th build of the job, holds test result at > > >>> >https://builds.apache.org/job/incubator-eagle-main/7/testReport/ > > >>> > > > >>> >Currently, I summed the failing test case as below, please anyone > who > > >>>is > > >>> >the owner try to fix them: > > >>> >org.apache.eagle.alert.cep.TestSiddhiEvaluator.test > > >>> >< > > >>> > > >>> > > https://builds.apache.org/job/incubator-eagle-main/7/testReport/org.apac > > >>>h > > >>> >e.eagle.alert.cep/TestSiddhiEvaluator/test/> > > >>> >org.apache.eagle.alert.dao.TestSiddhiStreamMetadataUtils.test > > >>> >< > > >>> > > >>> > > https://builds.apache.org/job/incubator-eagle-main/7/testReport/org.apac > > >>>h > > >>> >e.eagle.alert.dao/TestSiddhiStreamMetadataUtils/test/> > > >>> >org.apache.eagle.alert.dao.TestStreamDefinitionDAOImpl.test > > >>> >< > > >>> > > >>> > > https://builds.apache.org/job/incubator-eagle-main/7/testReport/org.apac > > >>>h > > >>> >e.eagle.alert.dao/TestStreamDefinitionDAOImpl/test/> > > >>> > > >>> > > > >>>>org.apache.eagle.alert.state.TestSiddhiStateSnapshotAndRestore.persiste > > >>>>nce > > >>> >Test7 > > >>> >< > > >>> > > >>> > > https://builds.apache.org/job/incubator-eagle-main/7/testReport/org.apac > > >>>h > > >>> > > > >>>>e.eagle.alert.state/TestSiddhiStateSnapshotAndRestore/persistenceTest7/ > > >>>>> > > >>> > > > >>> >Thanks. > > >>> >Michael > > >>> > > >>> > > >> > > > > >
