| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| | |\ |
|
| | | |\
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| |\| | | |
|
| | |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| |\| | | |
|
| | |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
|
| | | | | |
|
| |\| | | |
|
| | |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
processing.
THIS IS A VERY IMPORTANT ADDITION, see its doc for why.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
actually, the runtime dummy was missing some global entities, these
have now been added.
|
| | | |
| | |
| | |
| | |
| | | |
- added a test to check handling of damaged .qi files on startup
- made sure each test identifies itself on startup
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\| | |
|
| | | |
| | |
| | |
| | | |
Some devices seem to create them and I do not see any harm in supporting that.
|
| | | | |
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This was a result of an internal processing error if maximum field
sizes had been specified in the property replacer.
Also did some testbench improvements, including omstdout.
|
| |\| | |
|
| | | | |
|
| |\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was a complex manual merge, especially in action.c. So if
there occur some problems, this would be a good point to start
troubleshooting. I run a couple of tests before commiting and
they all went well.
Conflicts:
action.c
action.h
runtime/queue.c
runtime/queue.h
runtime/wti.c
runtime/wti.h
|
| | | |
| | |
| | |
| | | |
tests for the various timestamp formats have been added
|
| | | |
| | |
| | |
| | | |
this was a regression I introduced this afternoon
|
| |\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that this was NOT a trivial merge, and there may be
some issues. This needs to be seen when we continue developing.
Conflicts:
runtime/msg.h
runtime/obj.h
runtime/queue.c
runtime/srUtils.h
runtime/stream.c
runtime/stream.h
runtime/wti.c
tests/Makefile.am
tools/omfile.c
tools/syslogd.c
|
| | |/
| |
| |
| |
| |
| |
| | |
also adds speed, because you do no longer need to run the whole file
system in sync mode. New testbench and new config directives:
- $MainMsgQueueSyncQueueFiles
- $ActionQueueSyncQueueFiles
|
| | |
| |
| |
| |
| |
| |
| |
| | |
this permits us to keep a persistent test environment between
v4 and v5, most importantly using the same tools. As far as the
actual tests are concerned, some had issues. I had no time to check
if that was an issue with the test or an actual issue with the
v3/4 engine. Will do that at some later stage.
|
| |\|
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| | |\
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | | |\
| | | |
| | | |
| | | |
| | | | |
Conflicts:
tests/Makefile.am
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
is detected.
This change is considered important but small enough
to apply it directly to the stable version. [But it is a border case,
the change requires more code than I had hoped. Thus I have NOT tried
to actually catch all cases, this is left for the current devel
releases, if necessary]
|
| | | | |
|
| |\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
tests/diag.sh
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
... and now make check fails again, we have obviously found some new
bugs thanks to the additional cases
|
| |\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
tests/diskqueue.sh
tests/imtcp-multiport.sh
tests/manytcp.sh
tests/memq-persist.sh
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The imdiag module now can very effectively inject messages, which also
frees us from uncertainties of tcp reception and processing. All shell
script based tests have been modularized, what makes it far easier to
create new tests. Also, the test bench now executes more reliable and
much faster, because we can now rely on actual engine information where
we previously did just a dumb sleep.
|
| |\| |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | | | |
|
| |\| | |
|
| | | | |
|
