metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Foley <ma...@apache.org>
Subject Re: Tests failing due to new year
Date Tue, 03 Jan 2017 22:04:45 GMT
Heh, darn it, crossed in Jira – see METRON-648.  You win :-)

On 1/3/17, 1:13 PM, "Nick Allen" <nick@nickallen.org> wrote:

    Thanks, Kyle.  I am seeing the same issue.  Happy Y2K... I mean 2017.
    
    On Tue, Jan 3, 2017 at 4:09 PM, Kyle Richardson <kylerichardson2@gmail.com>
    wrote:
    
    > Created METRON-647 for tracking.
    >
    > -Kyle
    >
    > On Tue, Jan 3, 2017 at 3:49 PM, Kyle Richardson <kylerichardson2@gmail.com
    > >
    > wrote:
    >
    > > ** This is causing all new PRs to fail Travis CI **
    > >
    > > The rollover to the new year is causing unit test failures for some of
    > our
    > > parser classes. It looks like the issue in the same in all cases... We
    > have
    > > hard coded a timestamp assertion but the original message does not
    > contain
    > > the year and is now parsing as 2017 instead of 2016.
    > >
    > > I'm currently investigating the failure for BasicAsaParserTest.
    > > testIp6Addr:151.
    > >
    > > Other failures from the Travis CI log I'm looking at are:
    > >     GrokWebSphereParserTest.testParseLoginLine:60
    > >     GrokWebSphereParserTest.testParseMalformedLoginLine:151
    > >     GrokWebSphereParserTest.tetsParseLogoutLine:84
    > >     GrokWebSphereParserTest.tetsParseMalformedLogoutLine:175
    > >     GrokWebSphereParserTest.tetsParseMalformedOtherLine:220
    > >     GrokWebSphereParserTest.tetsParseMalformedRBMLine:198
    > >     GrokWebSphereParserTest.tetsParseOtherLine:129
    > >     GrokWebSphereParserTest.tetsParseRBMLine:107
    > >
    > > -Kyle
    > >
    > >
    >
    
    
    
    -- 
    Nick Allen <nick@nickallen.org>
    



Mime
View raw message