| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| |
| |
| | |
a3e48b697fa664110567fcd0027d24ea5a239041
... so that the testbench continues to work
|
| |
| |
| |
| | |
it permits to specifiy if asynchronous writing should be done or not
|
| | |
|
| |
| |
| |
| | |
On some platforms, the default is too low to carry out all test cases
|
| |
| |
| |
| | |
subsecond sleep did not work on all platforms
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
| |
properly initialized.
However, in practice the loader initializes them with zero, the
desired value, so there were no actual issue in almost all cases.
|
| |
|
| |
|
|
|
|
|
| |
note that so far no patch is provided. This has not yet been made
part of "make check"
|
|
|
|
| |
also improved nettester testbench tool a bit
|
| |
|
|
|
|
| |
the test cases actually have some races, not the code to be tested
|
| |
|
|
|
|
|
|
|
|
| |
The previous fix fixed an issue with on/off bying used in the exact wrong
semantic. It corrected the situation, but failed to fix one spot where the
wrong semantics were used. This is done with this commit.
Note that this is NOT a bug seen in any released version.
|
| |
|
| |
|
|
|
|
|
|
| |
Note that this introduces a test case that breaks the current code. This
commit does NOT yet provide the necessary code patch. Thus "make check"
does currently hang.
|
|
|
|
|
|
| |
Note that this introduces a test case that breaks the current code. This
commit does NOT yet provide the necessary code patch. Thus make check
does currently hang.
|
|
|
|
|
| |
this is an excerpt from some of the more intensen manual tests
I am doing, stripped down to be useful inside the testbench.
|
| |
|
|
|
|
| |
also improved testing tools to support new testcase structure
|
| |
|
| |
|
|
|
|
|
| |
this is a perquisite to support more flexible testing modes, which
could not intelligently be implemented with the old interface
|
|\ |
|
| |
| |
| |
| |
| |
| | |
disk queue mode did no longer work correctly. A side-effect of
this commit here is slightly cleaned-up (and more elegant) code
for circular files.
|
|/
|
|
|
|
| |
note that a buffer size calculation was done wrong, but this was cosmetic
because our buffers currently all use byte size, so even though the
formula was wrong, the result was correct.
|
|
|
|
|
|
|
|
|
|
| |
- improved testbench
- bugfix: potential data loss during file stream shutdown
- bugfix: potential problems during file stream shutdown
The shutdown/close sequence was not clean, what potentially (but
unlikely) could lead to some issues. We have not been able to describe
any fatal cases, but there was some bug potential. Sequence has now
been straighted out.
|
|
|
|
|
| |
primarily to ease migration from syslog-ng. See property replacer doc for
details. [backport from 5.5.3 because urgently needed by some]
|
|
|
|
|
|
|
| |
For consistency, ./configure generated "config.h" must be the first
header include through out the project.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|
|
|
|
| |
on some platforms (namely Debian sid). This smells like a bug in zlib.
Thanks to Michael Biebl for reporting the issue.
|
|
|
|
|
|
|
|
|
| |
- improved testbench to contain samples for totally malformed messages
which miss parts of the message content
- bugfix: some malformed messages could lead to a missing LF inside files
or some other missing parts of the template content.
- bugfix: if a message ended immediately with a hostname, the hostname
was mistakenly interpreted as TAG, and localhost be used as hostname
|
|
|
|
|
|
|
| |
[backported from v5 commit 98d1ed504ec001728955a5bcd7916f64cd85f39f]
This actually was a "recent" regression, but I did not realize that it
was introduced by the performance optimization in v4-devel. Shame on
me for having two devel versions at the same time...
|
| |
|
| |
|
|
|
|
|
| |
now CSV and regex extraction are being tested (would have caught the
bug fixed with the last commit).
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| |
| |
| |
| |
| |
| | |
This was a regression from the time() optimizations done in v4.
Bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=143
Thanks to Klaus Tachtler for reporting this bug.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
also prepared test case for TLS testing, but not activated it
inside the build itself.
A note on TLS testing: the current testsuite (in git!) already contains
TLS test cases. However, getting these test cases correct is not simple.
That's not a problem with the code itself, but rater a problem with
synchronization in the test environment. So I have deciced to keep the
TLS tests in, but not yet actually utilize them. This is most probably
left as an excercise for future (devel) releases.
|
| |
| |
| |
| |
| | |
... also improved two-instance test mechanism, now have a generic
approach.
|
| |
| |
| |
| | |
... plus a simple initial test of the tcp forwarding capability.
|
| | |
|
| |
| |
| |
| |
| | |
thus some unpredictable behavior and a false negative test result
could occur. [BACKPORTED from v5]
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
runtime/msg.c
|