Afraid not. What it saids is actually accurate - it didn’t say the application 
called “abort”. It saids that the job was aborted. There is a very different 
message when the application itself calls MPI_Abort.

> On Jan 6, 2019, at 1:19 PM, Jeff Wentworth via users 
> <> wrote:
> Hi everyone,
> Is there any way to suppress this bit of mpirun error chatter as shown in the 
> example below?  Since the code (a.out) already issues an error message and 
> error return status, I was hoping to leave it at that.  Not a show stopper by 
> any means, but was just wondering if maybe there was some other setting 
> available.  Also, the code in question gracefully exited and did not call 
> MPI_Abort(), so the portion of the mpirun message mentioning an abort could 
> confuse end users.
> Thanks.
> % mpirun -q -np 2 ./a.out blort.txt
> a.out: blort.txt: No such file or directory
> -------------------------------------------------------
> Primary job  terminated normally, but 1 process returned
> a non-zero exit code. Per user-direction, the job has been aborted.
> -------------------------------------------------------
> --------------------------------------------------------------------------
> _______________________________________________
> users mailing list

users mailing list

Reply via email to