Thomas,
here it is.
--
Best regards,
Eugene Istomin
On Tuesday, July 21, 2015 01:25:05 PM Thomas D. wrote:
> Hi,
>
> Eugene Istomin wrote:
> > 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/x
> > 86_64/liblognorm/_log
>
> On Gentoo x64 the test suite is passing ofr liblognorm-1.1.2:
> > # TOTAL: 36
> > # PASS: 36
> > # SKIP: 0
> > # XFAIL: 0
> > # FAIL: 0
> > # XPASS: 0
> > # ERROR: 0
>
> Can you please show us the content of "tests/test-suite.log"?
>
>
> -Thomas
>
>
> _______________________________________________
> 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.
============================================
liblognorm 1.1.2: tests/test-suite.log
============================================
# TOTAL: 36
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 35
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: parser_whitespace.sh
==========================
Using valgrind: no
===============================================================================
[parser_whitespace.sh]: test for whitespace in parser definition
Out:
JSONs weren't equal.
Expected:
{"num": "0x1234"}
Actual:
{ "field": { "f1": "1", "f2": 2 } }
FAIL: parser_LF.sh
==================
Using valgrind: no
===============================================================================
[parser_LF.sh]: test for LF in parser definition
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_hexnumber.sh
========================
Using valgrind: no
===============================================================================
[field_hexnumber.sh]: test for hexnumber field
Out:
{ "num": "0x1234" }
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_mac48.sh
====================
Using valgrind: no
===============================================================================
[field_mac48.sh]: test for dmac48 syntax
Out:
JSONs weren't equal.
Expected:
{"field": "f0:f6:1c:5f:cc:a2"}
Actual:
{ "num": "0x1234" }
FAIL: field_name_value.sh
=========================
Using valgrind: no
===============================================================================
[field_name_value.sh]: test for name/value parser
Out:
{ "field": { "f1": "1", "f2": 2 } }
JSONs weren't equal.
Expected:
{ "f": { "name": "value" } }
Actual:
{ "originalmsg": "ABCD:EF01:2345:6789:ABCD:EF01:2345:6789", "unparsed-data": "ABCD:EF01:2345:6789:ABCD:EF01:2345:6789" }
FAIL: field_kernel_timestamp.sh
===============================
Using valgrind: no
===============================================================================
[field_kernel_timestamp.sh]: test for kernel timestamp parser
Out:
{ "field": "f0:f6:1c:5f:cc:a2" }
JSONs weren't equal.
Expected:
{ "timestamp": "[12345.123456]"}
Actual:
{ "field": { "f1": "1", "f2": 2 } }
FAIL: field_whitespace.sh
=========================
Using valgrind: no
===============================================================================
[field_whitespace.sh]: test for whitespace parser
Out:
JSONs weren't equal.
Expected:
{ "b": "word2", "a": "word1" }
Actual:
{ "field": { "f1": "1", "f2": 2 } }
FAIL: field_rest.sh
===================
Using valgrind: no
===============================================================================
[field_rest.sh]: test for rest matches
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_json.sh
===================
Using valgrind: no
===============================================================================
[field_json.sh]: test for JSON field
Out:
JSONs weren't equal.
Expected:
{ "field": { "f1": "1", "f2": 2 } }
Actual:
{ "num": "0x1234" }
FAIL: field_cee-syslog.sh
=========================
Using valgrind: no
===============================================================================
[field_cee-syslog.sh]: test for JSON field
Out:
JSONs weren't equal.
Expected:
{ "field": { "f1": "1", "f2": 2 } }
Actual:
FAIL: field_ipv6.sh
===================
Using valgrind: no
===============================================================================
[field_ipv6.sh]: test for IPv6 parser
Out:
{ "num": "0x1234" }
JSONs weren't equal.
Expected:
{ "f": "ABCD:EF01:2345:6789:ABCD:EF01:2345:6789" }
Actual:
{ "num": "0x1234" }
FAIL: field_v2-iptables.sh
==========================
Using valgrind: no
===============================================================================
[field_v2-iptables.sh]: test for v2-iptables field
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_cef.sh
==================
Using valgrind: no
===============================================================================
[field_cef.sh]: test for CEF parser
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_checkpoint-lea.sh
=============================
Using valgrind: no
===============================================================================
[field_checkpoint-lea.sh]: test for Checkpoint LEA parser
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_duration.sh
=======================
Using valgrind: no
===============================================================================
[field_duration.sh]: test for duration syntax
Out:
{ "originalmsg": "duration 0:00:42 bytes", "unparsed-data": " bytes" }
JSONs weren't equal.
Expected:
{"field": "0:00:42"}
Actual:
FAIL: field_cisco-interface-spec.sh
===================================
Using valgrind: no
===============================================================================
[field_cisco-interface-spec.sh]: test for cisco-interface-spec syntax
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_tokenized.sh
========================
Using valgrind: no
===============================================================================
[field_tokenized.sh]: test for tokenized field
Out:
FAIL: field_tokenized_with_invalid_ruledef.sh
=============================================
Using valgrind: no
===============================================================================
[field_tokenized_with_invalid_ruledef.sh]: test for tokenized field with invalid rule definition
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_recursive.sh
========================
Using valgrind: no
===============================================================================
[field_recursive.sh]: test for recursive parsing field
Out:
{ "originalmsg": "123 abc 456 def", "unparsed-data": "123 abc 456 def" }
JSONs weren't equal.
Expected:
{"word": "123", "next": {"word": "abc", "next": {"word": "456", "next" : {"word": "def"}}}}
Actual:
{ "num": "15.9" }
blocked inbound via: 192.168.1.1 from: 1.2.3.4, 5.6.16.0\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5", "unparsed-data": "\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5" }
FAIL: field_tokenized_recursive.sh
==================================
Using valgrind: no
===============================================================================
[field_tokenized_recursive.sh]: test for tokenized field with recursive field matching tokens
Out:
{ "num": "15.9" }
blocked inbound via: 192.168.1.1 from: 1.2.3.4, 5.6.16.0\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5", "unparsed-data": "\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5" }
JSONs weren't equal.
Expected:
{
"addresses": [
{"ip_addr": "1.2.3.4"},
{"subnet_addr": "5.6.16.0", "subnet_mask": "12"},
{"ip_addr": "8.9.10.11"},
{"ip_addr": "12.13.14.15"},
{"subnet_addr": "16.17.18.0", "subnet_mask": "8"},
{"subnet_addr": "19.20.21.24", "subnet_mask": "3"}],
"server_ip": "192.168.1.5",
"via_ip": "192.168.1.1"}
Actual:
FAIL: field_interpret.sh
========================
Using valgrind: no
===============================================================================
[field_interpret.sh]: test for value interpreting field
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_interpret_with_invalid_ruledef.sh
=============================================
Using valgrind: no
===============================================================================
[field_interpret_with_invalid_ruledef.sh]: test for value interpreting field, with invalid ruledef
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_descent.sh
======================
Using valgrind: no
===============================================================================
[field_descent.sh]: test for descent based parsing field
Out:
{ "num": "15.9" }
blocked inbound via: 192.168.1.1 from: 1.2.3.4, 5.6.16.0\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5", "unparsed-data": "\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5" }
JSONs weren't equal.
Expected:
{"device": "gw-1", "net": {"ip_addr": "10.20.30.40"}, "tm": "2014-12-08T08:53:33.05+05:30"}
Actual:
FAIL: field_descent_with_invalid_ruledef.sh
===========================================
Using valgrind: no
===============================================================================
[field_descent_with_invalid_ruledef.sh]: test for descent based parsing field, with invalid ruledef
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_float.sh
====================
Using valgrind: no
===============================================================================
[field_float.sh]: test for float field
Out:
{ "num": "15.9" }
blocked inbound via: 192.168.1.1 from: 1.2.3.4, 5.6.16.0\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5", "unparsed-data": "\/12, 8.9.10.11, 12.13.14.15, 16.17.18.0\/8, 19.20.21.24\/3 to 192.168.1.5" }
JSONs weren't equal.
Expected:
{"num": "15.9"}
Actual:
FAIL: field_float_with_invalid_ruledef.sh
=========================================
Using valgrind: no
===============================================================================
[field_float_with_invalid_ruledef.sh]: test for float with invalid field-declaration
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_suffixed.sh
=======================
Using valgrind: no
===============================================================================
[field_suffixed.sh]: test for field with one of many possible suffixes
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_suffixed_with_invalid_ruledef.sh
============================================
Using valgrind: no
===============================================================================
[field_suffixed_with_invalid_ruledef.sh]: test for field with one of many possible suffixes, but invalid ruledef
liblognorm error: invalid field type 'suffixe'
Out:
{ "originalmsg": "reclaimed 559mb eden", "unparsed-data": "559mb eden" }
JSONs weren't equal.
Expected:
{ "originalmsg": "reclaimed 559mb eden", "unparsed-data": "559mb eden" }
Actual:
FAIL: field_regex_default_group_parse_and_return.sh
===================================================
Using valgrind: no
===============================================================================
[field_regex_default_group_parse_and_return.sh]: test for type ERE for regex field
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_regex_invalid_args.sh
=================================
Using valgrind: no
===============================================================================
[field_regex_invalid_args.sh]: test for invalid type for regex field with everything else defaulted
liblognorm error: cannot open file tmp.rulebase
fatal error: cannot load rulebase
FAIL: field_regex_with_consume_group.sh
=======================================
Using valgrind: no
===============================================================================
[field_regex_with_consume_group.sh]: test for regex field with consume-group
Out:
{ "rest": "8901abef", "first": "ad1234abcd,4567ef12," }
FAIL: field_regex_with_consume_group_and_return_group.sh
========================================================
Using valgrind: no
===============================================================================
[field_regex_with_consume_group_and_return_group.sh]: test for regex field with consume-group and return-group
++ add_rule 'rule=:%first:regex:[a-z]{2}(([a-f0-9]+),)+:0:2%%rest:rest%'
+++ rulebase_file_name
+++ '[' x == x ']'
+++ echo tmp.rulebase
++ local rb_file=tmp.rulebase
++ echo 'rule=:%first:regex:[a-z]{2}(([a-f0-9]+),)+:0:2%%rest:rest%'
++ execute ad1234abcd,4567ef12,8901abef
++ '[' x == xon ']'
++ echo ad1234abcd,4567ef12,8901abef
++ ../src/ln_test -oallowRegex -r tmp.rulebase -e json
++ echo Out:
Out:
++ cat test.out
{ "rest": "8901abef", "first": "4567ef12" }
++ '[' x == xon ']'
++ assert_output_contains '"first": "4567ef12"'
++ cat test.out
++ grep -F '"first": "4567ef12"'
{ "rest": "8901abef", "first": "4567ef12" }
++ assert_output_contains '"rest": "8901abef"'
++ cat test.out
++ grep -F '"rest": "8901abef"'
FAIL: field_regex_with_negation.sh
==================================
Using valgrind: no
===============================================================================
[field_regex_with_negation.sh]: test for regex field with negation
Out:
{ "rest": "8901abef", "first": "4567ef12" }
FAIL: field_tokenized_with_regex.sh
===================================
Using valgrind: no
===============================================================================
[field_tokenized_with_regex.sh]: test for tokenized field with regex based field
Out:
{ "rest": "foo", "first": "" }
bar", "first": "" }
FAIL: field_regex_while_regex_support_is_disabled.sh
====================================================
Using valgrind: no
===============================================================================
[field_regex_while_regex_support_is_disabled.sh]: test for field regex, while regex support is disabled
Out:
{ "rest": "foo", "first": "" }
bar", "first": "" }
_______________________________________________
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.
