rsyslog/tests/imuxsock_logger_err.sh
Rainer Gerhards 6bba5a7577
testbench: guard tests against unexpected warning messages
Practice has shown that environment-induced error messages may
appear during test runs. For example, incorrect resolver settings
may cause name resolution warnings or errors. These are unrelated
to the test itself.

This patch enables tests that are otherwise unaffected by the faillures
to continue and provide "pass" test result.

see also https://github.com/rsyslog/rsyslog/issues/4619
2021-08-09 10:41:09 +02:00

30 lines
1.1 KiB
Bash
Executable File

#!/bin/bash
# this is primarily a safeguard to ensure the imuxsock tests basically work
# added 2014-12-04 by Rainer Gerhards, licensed under ASL 2.0
echo \[imuxsock_logger.sh\]: test imuxsock
. ${srcdir:=.}/diag.sh init
check_logger_has_option_d
generate_conf
add_conf '
module(load="../plugins/imuxsock/.libs/imuxsock" sysSock.use="off")
input(type="imuxsock" Socket="'$RSYSLOG_DYNNAME'-testbench_socket")
template(name="outfmt" type="string" string="%msg:%\n")
*.=notice action(type="omfile" file=`echo $RSYSLOG_OUT_LOG` template="outfmt")
'
startup
# send a message with trailing LF
logger -d -u $RSYSLOG_DYNNAME-testbench_socket "wrong message"
# the sleep below is needed to prevent too-early termination of rsyslogd
./msleep 100
shutdown_when_empty # shut down rsyslogd when done processing messages
wait_shutdown # we need to wait until rsyslogd is finished!
cmp $RSYSLOG_OUT_LOG $srcdir/resultdata/imuxsock_logger.log
if [ $? -eq 0 ]; then
echo "imuxsock_logger_err.sh did not report an error where it should!"
exit 1
else
echo "all well, we saw the error that we wanted to have"
fi;
exit_test