Description of problem:
In the current runner framework we always return the pid i.e ret value of the waitpid, as said above it is not the exit value of the child process
Version-Release number of selected component (if applicable):
returning the ret value of waitpid()
extract the exit code and return the actual exit status of the child process
REVIEW: http://review.gluster.org/14042 (runner: extract and return actual exit status of child) posted (#1) for review on master by Prasanna Kumar Kalever (email@example.com)
COMMIT: http://review.gluster.org/14042 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Prasanna Kumar Kalever <email@example.com>
Date: Thu Apr 21 14:38:16 2016 +0530
runner: extract and return actual exit status of child
pid_t waitpid(pid_t pid, int *status, int options);
The waitpid() system call suspends execution of the calling process
until a child specified by pid argument has changed state.
Here the ret (pid) value is not equal to the exit status of the child process.
Check manpages for more info on this.
In the current runner framework we always return the pid i.e ret value
of the waitpid, as said above it is not the exit value of the child process
Extract the actual exit code/status in case if the child terminated normally,
that is, by calling exit(3) or _exit(2), or by returning from main()
Signed-off-by: Prasanna Kumar Kalever <firstname.lastname@example.org>
Tested-by: Prasanna Kumar Kalever <email@example.com>
Reviewed-by: Kaleb KEITHLEY <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
will be tracked under 1322306
sorry updated it by mistake, taking my comments back
It is just modified in master
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.