tests/logsv/saflogtest.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
saflogtest is not returning appropriate exit code to the shell when
SaLogWriteLogCallbackT fails either because of an error reported in the
callback or because
of an invalid invocationId.
The patch exits with EXIT_FAILURE in these scenarios.
diff --git a/tests/logsv/saflogtest.c b/tests/logsv/saflogtest.c
--- a/tests/logsv/saflogtest.c
+++ b/tests/logsv/saflogtest.c
@@ -170,12 +170,12 @@ static SaAisErrorT write_log_record(SaLo
if (cb_invocation != invocation) {
fprintf(stderr, "logWriteLogCallbackT FAILED: wrong
invocation\n");
- return errorCode;
+ return SA_AIS_ERR_BAD_OPERATION;
}
if ((cb_error != SA_AIS_ERR_TRY_AGAIN) && (cb_error !=
SA_AIS_OK)) {
fprintf(stderr, "logWriteLogCallbackT FAILED: %u\n",
cb_error);
- return errorCode;
+ return cb_error;
}
if (cb_error == SA_AIS_ERR_TRY_AGAIN) {
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
