2014-12-05 18:45 GMT+01:00 David Lang <[email protected]>: > As a suggestion, we should setup the tests against the testing branch to > run with a couple different configs. (I'm assuming that it currently tests > a "kitchen sink" config, i.e. everything enabled) > > I would suggest that we do > > 1. "kitchen sink" config, everything enabled > 2. "minimum" config, minimum syslog replacement, tcp/udp/files, everything > else disabled > > these two definitely make sense
> #2 it to catch cases like the ptcp test that are enabled when they > shouldn't be > > and then if the distro maintainers can pass along their configs, we should > add them as well. > > these as well ... but given the fact that the testbench grows and takes a while to complete, I will probably run out of resorces to do all this testing. Also, a system needs to be developed to track success/failure for these tests. Right now, I do the latter manually, and even this tends to be a mess at times. Rainer > David Lang > > > On Fri, 5 Dec 2014, Rainer Gerhards wrote: > > 2014-12-05 16:13 GMT+01:00 singh.janmejay <[email protected]>: >> >> Im the culprit. >>> >> >> >> Me as well. I should have seen that when I merged. I'll hunt for the >> commit >> in question. >> >> Rainer >> >> >> The patches for tests for rscript functions replace and >>> wrap went in 2 sets. One which had EXTRA_DIST entries missing. I think >>> second set is a part of an open PR. Which is why its not part of 8.6.0. >>> Sorry for the confusion. >>> >>> mmjsonparse it seems is trying to load ptcp, did you enable ptcp in >>> configure? >>> >>> >>> >>> On Fri, Dec 5, 2014 at 8:04 PM, Thomas D. <[email protected]> wrote: >>> >>> > Hi, >>> > >>> > On 2014-12-05 13:01, Rainer Gerhards wrote: >>> > > Thanks. It looks like it cannot find the conf file for some (yet >>> unkonwn) >>> > > reason. >>> > >>> > Rainer, the rsyslog-8.6.0 release tarball [1] doesn't contain a file >>> > like "rscript_replace.conf", "gethostname.conf"... >>> > >>> > I tried to build from git master and the test suite passed, well 2 >>> failed: >>> > >>> > ========================================= >>> > rsyslog 8.6.0: tests/test-suite.log >>> > ========================================= >>> > >>> > # TOTAL: 104 >>> > # PASS: 97 >>> > # SKIP: 5 >>> > # XFAIL: 0 >>> > # FAIL: 2 >>> > # XPASS: 0 >>> > # ERROR: 0 >>> > >>> > .. contents:: :depth: 2 >>> > >>> > SKIP: sndrcv_udp.sh >>> > =================== >>> > >>> > >>> > >>> ============================================================ >>> =================== >>> > [sndrcv_udp.sh]: testing sending and receiving via udp >>> > >>> > SKIP: imuxsock_logger_root.sh >>> > ============================= >>> > >>> > [imuxsock_logger_root.sh]: test trailing LF handling in imuxsock >>> > This test must be run as root with no other active syslogd >>> > >>> > SKIP: imuxsock_traillf_root.sh >>> > ============================== >>> > >>> > [imuxsock_traillf_root.sh]: test trailing LF handling in imuxsock >>> > This test must be run as root with no other active syslogd >>> > >>> > SKIP: imuxsock_ccmiddle_root.sh >>> > =============================== >>> > >>> > [imuxsock_ccmiddle_root.sh]: test trailing LF handling in imuxsock >>> > This test must be run as root with no other active syslogd >>> > >>> > FAIL: mmjsonparse_simple.sh >>> > =========================== >>> > >>> > >>> > >>> ============================================================ >>> =================== >>> > [mmjsonparse_simple.sh]: basic test for mmjsonparse module with >>> defaults >>> > rsyslogd: could not load module '../plugins/imptcp/.libs/imptcp.so', >>> > dlopen: ../plugins/imptcp/.libs/imptcp.so: cannot open shared object >>> > file: No such file or directory [try http://www.rsyslog.com/e/2066 ] >>> > rsyslogd: input module name 'imptcp' is unknown [try >>> > http://www.rsyslog.com/e/2209 ] >>> > rsyslogd: error during parsing file >>> > ./testsuites/mmjsonparse_simple.conf, on or before line 6: parameter >>> > 'port' not known -- typo in config file? [try >>> > http://www.rsyslog.com/e/2207 ] >>> > rsyslogd started with pid 50217 >>> > connect(): Connection refused >>> > connect() failed >>> > error in trying to open connection i=0 >>> > error opening connections >>> > error during tcpflood! see rsyslog.out.log.save for what was written >>> > cp: cannot stat ‘rsyslog.out.log’: No such file or directory >>> > >>> > FAIL: mmjsonparse_cim.sh >>> > ======================== >>> > >>> > >>> > >>> ============================================================ >>> =================== >>> > [mmjsonparse_cim.sh]: basic test for mmjsonparse module with cim cookie >>> > rsyslog.pid exists, trying to shut down rsyslogd process 50217. >>> > rsyslogd: could not load module '../plugins/imptcp/.libs/imptcp.so', >>> > dlopen: ../plugins/imptcp/.libs/imptcp.so: cannot open shared object >>> > file: No such file or directory [try http://www.rsyslog.com/e/2066 ] >>> > rsyslogd: input module name 'imptcp' is unknown [try >>> > http://www.rsyslog.com/e/2209 ] >>> > rsyslogd: error during parsing file ./testsuites/mmjsonparse_cim.conf, >>> > on or before line 6: parameter 'port' not known -- typo in config file? >>> > [try http://www.rsyslog.com/e/2207 ] >>> > rsyslogd started with pid 50251 >>> > connect(): Connection refused >>> > connect() failed >>> > error in trying to open connection i=0 >>> > error opening connections >>> > error during tcpflood! see rsyslog.out.log.save for what was written >>> > cp: cannot stat ‘rsyslog.out.log’: No such file or directory >>> > >>> > SKIP: omod-if-array.sh >>> > ====================== >>> > >>> > [omod-if-array.sh]: test omod-if-array via udp >>> > NOTE: the interface checked with this test is currently NOT >>> > supported. We may support it again in the future. So for now, >>> > we just skip this test and do not remove it. >>> > >>> > >>> > >>> > => However, the release tarball is invalid :( >>> > >>> > >>> > -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. >>> > >>> >>> >>> >>> -- >>> Regards, >>> Janmejay >>> http://codehunk.wordpress.com >>> _______________________________________________ >>> 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. > > > _______________________________________________ > 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.
