It affects only the test suite.
--
Regards,
Janmejay
PS: Please blame the typos in this mail on my phone's uncivilized soft
keyboard sporting it's not-so-smart-assist technology.
On Dec 9, 2014 6:35 PM, "Thomas D." wrote:
> Hi,
>
> On 2014-12-09 13:58, Rainer Gerhards wrote:
> >> The current v
Hi,
On 2014-12-09 13:58, Rainer Gerhards wrote:
>> The current v8.6.0 release tarball is invalid, but does it only affects
>> the test suite?
>
> What does "invalid" mean? You mean the testbench failures? Then I would say
> the tarball is valid, but there are some bugs.
The problems I have seen
2014-12-09 13:54 GMT+01:00 Thomas D. :
> Hi,
>
> I am not sure about the current status and if I should make
> rsyslog-8.6.0 available within Gentoo or wait for the next release:
>
> The current v8.6.0 release tarball is invalid, but does it only affects
> the test suite?
>
What does "invalid" me
Hi,
I am not sure about the current status and if I should make
rsyslog-8.6.0 available within Gentoo or wait for the next release:
The current v8.6.0 release tarball is invalid, but does it only affects
the test suite?
We currently don't support testing of rsyslog in Gentoo. I planned to
add te
Noted. Thanks for correcting.
On Sat, Dec 6, 2014 at 10:27 PM, Rainer Gerhards
wrote:
> Janmejay,
>
> please have a look here:
>
>
> https://github.com/rsyslog/rsyslog/commit/2507387338f7c147b7816bf4390c2e289a14091a
>
> It's a subtle issue, I just wanted to make you aware of it for future
> cont
Janmejay,
please have a look here:
https://github.com/rsyslog/rsyslog/commit/2507387338f7c147b7816bf4390c2e289a14091a
It's a subtle issue, I just wanted to make you aware of it for future
contributions :-)
@all: there are still more path issues in "make distcheck", but they are
hard to tackle
2014-12-05 18:45 GMT+01:00 David Lang :
> 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" c
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, min
2014-12-05 16:13 GMT+01:00 singh.janmejay :
> 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
> se
Thx, I'll shuffle the test into a imtcp section.
Rainer
2014-12-05 17:22 GMT+01:00 Thomas D. :
> Hi,
>
> On 2014-12-05 16:30, singh.janmejay wrote:
> > Yes. But does the test pass with imptcp enabled?
>
> Yup, with imptcp enabled, the test suite will pass (git master).
>
>
> -Thomas
>
>
Hi,
On 2014-12-05 16:30, singh.janmejay wrote:
> Yes. But does the test pass with imptcp enabled?
Yup, with imptcp enabled, the test suite will pass (git master).
-Thomas
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http
Yes. But does the test pass with imptcp enabled?
On Fri, Dec 5, 2014 at 8:58 PM, Thomas D. wrote:
> On 2014-12-05 16:13, singh.janmejay wrote:
> > mmjsonparse it seems is trying to load ptcp, did you enable ptcp in
> > configure?
>
> imptcp was not enabled:
>
> /var/tmp/portage/app-admin/rsyslog
On 2014-12-05 16:13, singh.janmejay wrote:
> mmjsonparse it seems is trying to load ptcp, did you enable ptcp in
> configure?
imptcp was not enabled:
/var/tmp/portage/app-admin/rsyslog-8./work/rsyslog-8./configure
--prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--mand
Im the culprit. 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 enabl
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 t
2014-12-05 11:58 GMT+01:00 Thomas D. :
> Hi,
>
> On 2014-12-05 11:12, Rainer Gerhards wrote:
> > Is this "make check" or "make distcheck". I ask because I have seen some
> > problems with "make distcheck" where I think some pathes are not correct.
> > If it is just "make check", can you please mai
Hi,
On 2014-12-05 11:12, Rainer Gerhards wrote:
> Is this "make check" or "make distcheck". I ask because I have seen some
> problems with "make distcheck" where I think some pathes are not correct.
> If it is just "make check", can you please mail me the failing tests' log
> files.
Simple "make
Is this "make check" or "make distcheck". I ask because I have seen some
problems with "make distcheck" where I think some pathes are not correct.
If it is just "make check", can you please mail me the failing tests' log
files.
Thanks,
Rainer
2014-12-04 23:37 GMT+01:00 Thomas D. :
> Hi,
>
> the
Hi,
the test suite for the final 8.6.0 release is failing on my systems:
=
rsyslog 8.6.0: tests/test-suite.log
=
# TOTAL: 119
# PASS: 103
# SKIP: 5
# XFAIL: 0
# FAIL: 11
# XPASS: 0
# ERROR: 0
.. contents:: :de
That module was a hack to do structured data in a non standard wax over
3164. The regular 5424 parser handles that.
Sent from phone, thus brief.
Am 04.12.2014 19:07 schrieb "David Lang" :
> with the pmrfc3164sd module being removed, is there a special module
> needed to get at that structured dat
with the pmrfc3164sd module being removed, is there a special module needed to
get at that structured data of does the rfc5425 module do that?
David Lang
On Thu, 4 Dec 2014, Thomas D. wrote:
Hi,
I am missing the following information from the changelogs:
- imttcp was removed
- pmrfc3164sd w
Hi,
On 2014-12-04 15:19, Rainer Gerhards wrote:
> I am interested, though, in your build of omoracle. Did the build actually
> work? There are user reports going back to the early v7 (or even v6) days
> that the module didn't even build, much less work. As nobody turned up to
> fix it, I finally r
2014-12-04 14:57 GMT+01:00 Thomas D. :
> Hi,
>
> I am missing the following information from the changelogs:
>
> - imttcp was removed
> - pmrfc3164sd was removed
> - omoracle was removed
>
> I didn't know these modules at all, but we had build support for these
> modules until today in Gentoo. Whi
Hi,
I am missing the following information from the changelogs:
- imttcp was removed
- pmrfc3164sd was removed
- omoracle was removed
I didn't know these modules at all, but we had build support for these
modules until today in Gentoo. While preparing the 8.6.0 release I
stumbled across the "unr
Hi all,
We have released rsyslog 8.6.0.
This is the first stable release under a new release cycle and versioning
scheme. This new scheme is important news in itself. For more details,
please have a look here:
http://www.rsyslog.com/rsyslogs-new-release-cycle-and-versioning-scheme/
Version 8.6.
25 matches
Mail list logo
