Hello,

from OBS build log:
[  178s] Testsuite summary for liblognorm 1.1.2
[  178s] 
============================================================================
[  178s] # TOTAL: 36
[  178s] # PASS:  10
[  178s] # SKIP:  0
[  178s] # XFAIL: 0
[  178s] # FAIL:  26
[  178s] # XPASS: 0
[  178s] # ERROR: 0


Here is full log:
https://build.opensuse.org/build/home:conecenter:suse:rev4/openSUSE_13.2/x86_64/liblognorm/_log
 


-- 
Best regards,
Eugene Istomin


On Monday, July 20, 2015 05:52:39 PM Florian Riedl wrote:
> Hi all,
> 
> we have just released liblognorm 1.1.2. This release contains new parser
> syntaxes and some fixes.
> 
> Changes:
> Version 1.1.2, 2015-07-20
> 
>    - permit newline inside parser definition
>    - new parser “cisco-interface-spec”
>    - new parser “json” to process json parts of the message
>    - new parser “mac48″ to process mac layer addresses
>    - new parser “name-value-list” (currently inofficial, experimental)
>    - some parsers did incorrectly report success when an error occurred
>    this was caused by inconsistencies between various macros. We have
>    changed the parser-generation macros to match the semantics of the
>    broader CHKN/CHKR macros and also restructured/simplified the
>    parser generation macros.
>    closes https://github.com/rsyslog/liblognorm/issues/41
>    - call “rest” parser only if nothing else matches.
>    Versions prior to 1.1.2 did execute “rest” during regular parser
>    processing, and thus parser matches have been more or less random.
>    With 1.1.2 this is now always the last parser called. This may cause
>    problems with existing rulesets, HOWEVER, adding any other rule or
>    changing the load order would also have caused problems, so there
>    really is no compatibility to preserve.
>    see also:
> 
>   
> http://blog.gerhards.net/2015/04/liblognorms-rest-parser-now-more-useful.ht
> ml - new API to support error callbacks
>    This permits callers to forward messages in regard to e.g. wrong rule
>    bases to their users, which is very useful and actually missing in the
>    previous code base. So far, we only have few error messages.
>    However, we will review the code and add more. The important part is
>    that callers can begin to use the new API and thus will benefit when
>    we add more error messages.
>    - testbench is now enabled by default
>    - bugfix: misadressing on some constant values
>    see also https://github.com/rsyslog/liblognorm/pull/67
>    Thanks to github user ontholerian for the patch
>    - bugfix: add missing function prototypes
>    This could potentially lead to problems on some platforms,
>    especially those with 64 bit pointers.
> 
> Download:
> http://www.liblognorm.com/download/liblognorm-1-1-2/
> 
> As always, feedback is appreciated.
> 
> Best regards,
> Florian Riedl
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T
> LIKE THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to