All of the test scripts are calling diag.sh with a single parameter of 'init'. At line 48, your diag.sh is testing against $2, and it's unset. Is your bash environment/profile/whatever turning on the nounset warning? It may just be your personal environment turning on some warnings that the tests are assuming are not enabled. See: http://www.gnu.org/software/bash/manual/bash.html#The-Set-Builtin and search for -u and nounset.
"-u Treat unset variables and parameters other than the special parameters ‘@’ or ‘*’ as an error when performing parameter expansion. An error message will be written to the standard error, and a non-interactive shell will exit." So you need to find where -u or -o nounset is being used, and remove it. Sample script to display behavior: #!/bin/bash # if I uncomment the next line, I get the 'unbound variable' error like your log is displaying. # set -o nounset if [ "X$2" == "X" ]; then echo foo else echo bar fi $ bash foo.sh foo.sh: line 5: $2: unbound variable $ bash foo.sh bar baz Bar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of James Chang Sent: Friday, September 11, 2015 11:29 AM To: rsyslog-users <[email protected]> Subject: [rsyslog] 8.12.0 testsuite failures on Solaris Hi rsyslog users, I've attached the testsuite log in which only the config validation test passes - yikes. Could someone point me in the right direction to find what's missing? I'm already using RS_SORTCMD=gsort. Thanks, James _______________________________________________ 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.
