Re: [OMPI users] Hide Abort output
Indeed, it seems that it addresses what I want! I read the discussions on the MPI Forum list, which is very interesting. I began to develop a terminaison code before seeing that the use of MPI_Abort() should be sufficient. But I didn't post anything, since my case is particular: I have iterative computations. Thus, I can check if any terminaison message has been received at some points (with the async receive at the beginning of the program) -- the sending of messages has to be done in a "recursive" way to ensure a smaller number of messages exchanged between tasks, because there's not "multicast" way of sending something. In my case, I don't need special ending requirements if tasks share files, etc., which is not the general case of the standardization of an API. But I still think that an MPI_Quit() would be very usefull. Thank you very much! .Yves. Le Tuesday 06 April 2010 22:40:29 Jeff Squyres, vous avez écrit : > BTW, we diverged quite a bit on this thread -- Yves -- does the > functionality that was fixed by Ralph address your original issue? > > On Apr 2, 2010, at 10:21 AM, Ralph Castain wrote: > > Testing found that I had missed a spot here, so we weren't fully > > suppressing messages (including MPI_Abort). So the corrected fix is in > > r22926, and will be included in tonight's tarball. > > > > I also made --quiet be a new MCA param orte_execute_quiet so you can put > > it in your environment instead of only on the cmd line. > > > > HTH > > Ralph > > > > On Apr 2, 2010, at 1:18 AM, Ralph Castain wrote: > > > Actually, a cmd line option to mpirun already existed for this purpose. > > > Unfortunately, it wasn't properly being respected, so even knowing > > > about it wouldn't have helped. > > > > > > I have fixed this as of r22925 on our developer's trunk and started the > > > script to generate a fresh nightly tarball. Give it a little time and > > > then you can find it on the web site: > > > > > > http://www.open-mpi.org/nightly/trunk/ > > > > > > Use the -q or --quiet option and the message will be suppressed. I will > > > request that this be included in the upcoming 1.4.2 and 1.5.0 releases. > > > > > > On Apr 1, 2010, at 8:38 PM, Yves Caniou wrote: > > >> For information, I use the debian-packaged OpenMPI 1.4.1. > > >> > > >> Cheers. > > >> > > >> .Yves. > > >> > > >> Le Wednesday 31 March 2010 12:41:34 Jeff Squyres (jsquyres), vous avez écrit : > > >>> At present there is no such feature, but it should not be hard to > > >>> add. > > >>> > > >>> Can you guys be a little more specific about exactly what you are > > >>> seeing and exactly what you want to see? (And what version you're > > >>> working with - I'll caveat my discussion that this may be a > > >>> 1.5-and-forward thing) > > >>> > > >>> -jms > > >>> Sent from my PDA. No type good. > > >>> > > >>> - Original Message - > > >>> From: users-boun...@open-mpi.org > > >>> To: Open MPI Users > > >>> Sent: Wed Mar 31 05:38:48 2010 > > >>> Subject: Re: [OMPI users] Hide Abort output > > >>> > > >>> > > >>> I have to say this is a very common issue for our users. They > > >>> repeatedly report the long Open MPI MPI_Abort() message in help > > >>> queries and fail to look for the application error message about the > > >>> root cause. A short MPI_Abort() message that said "look elsewhere > > >>> for the real error message" would be useful. > > >>> > > >>> Cheers, > > >>> David > > >>> > > >>> On 03/31/2010 07:58 PM, Yves Caniou wrote: > > >>>> Dear all, > > >>>> > > >>>> I am using the MPI_Abort() command in a MPI program. > > >>>> I would like to not see the note explaining that the command caused > > >>>> Open MPI to kill all the jobs and so on. > > >>>> I thought that I could find a --mca parameter, but couldn't grep it. > > >>>> The only ones deal with the delay and printing more information (the > > >>>> stack). > > >>>> > > >>>> Is there a mean to avoid the printing of the note (except the > > >>>> 2>/dev/null tip
Re: [OMPI users] Hide Abort output
BTW, we diverged quite a bit on this thread -- Yves -- does the functionality that was fixed by Ralph address your original issue? On Apr 2, 2010, at 10:21 AM, Ralph Castain wrote: > Testing found that I had missed a spot here, so we weren't fully suppressing > messages (including MPI_Abort). So the corrected fix is in r22926, and will > be included in tonight's tarball. > > I also made --quiet be a new MCA param orte_execute_quiet so you can put it > in your environment instead of only on the cmd line. > > HTH > Ralph > > On Apr 2, 2010, at 1:18 AM, Ralph Castain wrote: > > > Actually, a cmd line option to mpirun already existed for this purpose. > > Unfortunately, it wasn't properly being respected, so even knowing about it > > wouldn't have helped. > > > > I have fixed this as of r22925 on our developer's trunk and started the > > script to generate a fresh nightly tarball. Give it a little time and then > > you can find it on the web site: > > > > http://www.open-mpi.org/nightly/trunk/ > > > > Use the -q or --quiet option and the message will be suppressed. I will > > request that this be included in the upcoming 1.4.2 and 1.5.0 releases. > > > > > > On Apr 1, 2010, at 8:38 PM, Yves Caniou wrote: > > > >> For information, I use the debian-packaged OpenMPI 1.4.1. > >> > >> Cheers. > >> > >> .Yves. > >> > >> Le Wednesday 31 March 2010 12:41:34 Jeff Squyres (jsquyres), vous avez > >> écrit : > >>> At present there is no such feature, but it should not be hard to add. > >>> > >>> Can you guys be a little more specific about exactly what you are seeing > >>> and exactly what you want to see? (And what version you're working with - > >>> I'll caveat my discussion that this may be a 1.5-and-forward thing) > >>> > >>> -jms > >>> Sent from my PDA. No type good. > >>> > >>> - Original Message - > >>> From: users-boun...@open-mpi.org > >>> To: Open MPI Users > >>> Sent: Wed Mar 31 05:38:48 2010 > >>> Subject: Re: [OMPI users] Hide Abort output > >>> > >>> > >>> I have to say this is a very common issue for our users. They repeatedly > >>> report the long Open MPI MPI_Abort() message in help queries and fail to > >>> look for the application error message about the root cause. A short > >>> MPI_Abort() message that said "look elsewhere for the real error message" > >>> would be useful. > >>> > >>> Cheers, > >>> David > >>> > >>> On 03/31/2010 07:58 PM, Yves Caniou wrote: > >>>> Dear all, > >>>> > >>>> I am using the MPI_Abort() command in a MPI program. > >>>> I would like to not see the note explaining that the command caused Open > >>>> MPI to kill all the jobs and so on. > >>>> I thought that I could find a --mca parameter, but couldn't grep it. The > >>>> only ones deal with the delay and printing more information (the stack). > >>>> > >>>> Is there a mean to avoid the printing of the note (except the 2>/dev/null > >>>> tips)? Or to delay this printing? > >>>> > >>>> Thank you. > >>>> > >>>> .Yves. > >>> > >>> ___ > >>> users mailing list > >>> us...@open-mpi.org > >>> http://www.open-mpi.org/mailman/listinfo.cgi/users > >> > >> > >> > >> -- > >> Yves Caniou > >> Associate Professor at Université Lyon 1, > >> Member of the team project INRIA GRAAL in the LIP ENS-Lyon, > >> Délégation CNRS in Japan French Laboratory of Informatics (JFLI), > >> * in Information Technology Center, The University of Tokyo, > >> 2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan > >> tel: +81-3-5841-0540 > >> * in National Institute of Informatics > >> 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan > >> tel: +81-3-4212-2412 > >> http://graal.ens-lyon.fr/~ycaniou/ > >> > >> ___ > >> users mailing list > >> us...@open-mpi.org > >> http://www.open-mpi.org/mailman/listinfo.cgi/users > > > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI users] Hide Abort output
For those wishing to follow the thread Dick started on the MPI forum list: http://lists.mpi-forum.org/mpi-forum/2010/04/0606.php On Apr 6, 2010, at 2:31 PM, Richard Treumann wrote: > The MPI standard says that MPI_Abort makes a "best effort". It also says that > an MPI implementation is free to lose the value passed into MPI_Abort and > deliver some other RC.. > > The standard does not say that MPI_Abort becomes a valid way to end a > parallel job if it is passed a zero. > > To me it seems pretty clear the name MPI_Abort is was chosen to imply failure. > > I think modifying the standard to be explicit about what must happen when > MPI_Abort is passed zero would be an option. It is a ugly one in my view but > it would give this kind of application the equivalent of MPI_Quit. > > Right now, someone who passes a zero to MPI_Abort would have a hard time > claiming his application is valid. > > Dick > > > Dick Treumann - MPI Team > IBM Systems & Technology Group > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > Tele (845) 433-7846 Fax (845) 433-8363 > > > "Terry Frankcombe" ---04/06/2010 01:33:53 PM---> Jeff - > > > > From: > "Terry Frankcombe" > > To: > "Open MPI Users" > > Date: > 04/06/2010 01:33 PM > > Subject: > Re: [OMPI users] Hide Abort output > > Sent by: > users-boun...@open-mpi.org > > > > > Jeff - > > > > I started a discussion of MPI_Quit on the MPI Forum reflector. I raised > > the question because I do not think using MPI_Abort is appropriate. > > > > The situation is when a single task decides the parallel program has > > arrived at the desired answer and therefore whatever the other tasks are > > currently doing has become irrelevant. The other tasks do not know that > > the answer has been found by one of them so they cannot just call > > MPI_Finalize. > > > > Do we need a clean and portable way for the task that detects that the > > answer has been found and written out to do a single handed termination of > > the parallel job? > > I'm not Jeff. But isn't that MPI_Abort with an appropriate errorcode > argument, provided we can get it to shut up? > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI users] Hide Abort output
The MPI standard says that MPI_Abort makes a "best effort". It also says
that an MPI implementation is free to lose the value passed into MPI_Abort
and deliver some other RC..
The standard does not say that MPI_Abort becomes a valid way to end a
parallel job if it is passed a zero.
To me it seems pretty clear the name MPI_Abort is was chosen to imply
failure.
I think modifying the standard to be explicit about what must happen when
MPI_Abort is passed zero would be an option. It is a ugly one in my view
but it would give this kind of application the equivalent of MPI_Quit.
Right now, someone who passes a zero to MPI_Abort would have a hard time
claiming his application is valid.
Dick
Dick Treumann - MPI Team
IBM Systems & Technology Group
Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601
Tele (845) 433-7846 Fax (845) 433-8363
From: "Terry Frankcombe"
To: "Open MPI Users"
Date: 04/06/2010 01:33 PM
Subject:Re: [OMPI users] Hide Abort output
Sent by:users-boun...@open-mpi.org
> Jeff -
>
> I started a discussion of MPI_Quit on the MPI Forum reflector. I raised
> the question because I do not think using MPI_Abort is appropriate.
>
> The situation is when a single task decides the parallel program has
> arrived at the desired answer and therefore whatever the other tasks are
> currently doing has become irrelevant. The other tasks do not know that
> the answer has been found by one of them so they cannot just call
> MPI_Finalize.
>
> Do we need a clean and portable way for the task that detects that the
> answer has been found and written out to do a single handed termination
of
> the parallel job?
I'm not Jeff. But isn't that MPI_Abort with an appropriate errorcode
argument, provided we can get it to shut up?
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Hide Abort output
> Jeff - > > I started a discussion of MPI_Quit on the MPI Forum reflector. I raised > the question because I do not think using MPI_Abort is appropriate. > > The situation is when a single task decides the parallel program has > arrived at the desired answer and therefore whatever the other tasks are > currently doing has become irrelevant. The other tasks do not know that > the answer has been found by one of them so they cannot just call > MPI_Finalize. > > Do we need a clean and portable way for the task that detects that the > answer has been found and written out to do a single handed termination of > the parallel job? I'm not Jeff. But isn't that MPI_Abort with an appropriate errorcode argument, provided we can get it to shut up?
Re: [OMPI users] Hide Abort output
Jeff - I started a discussion of MPI_Quit on the MPI Forum reflector. I raised the question because I do not think using MPI_Abort is appropriate. The situation is when a single task decides the parallel program has arrived at the desired answer and therefore whatever the other tasks are currently doing has become irrelevant. The other tasks do not know that the answer has been found by one of them so they cannot just call MPI_Finalize. Do we need a clean and portable way for the task that detects that the answer has been found and written out to do a single handed termination of the parallel job? Dick Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 From: Jeff Squyres To: , "Open MPI Users" Date: 04/06/2010 09:35 AM Subject:Re: [OMPI users] Hide Abort output Sent by:users-boun...@open-mpi.org I'm not sure I understand what your MPI_Quit function would do differently than MPI_Abort and/or MPI_Finalize...? On Apr 6, 2010, at 3:13 AM, Yves Caniou wrote: > I really understand the failure idea of the MPI_Abort() function, and it > clearly appeared in the recent mails. > > There is an evident advantage for me to have an MPI_Quit() function: > Having such a function would be great in the sens that someone would not have > to code the termination mechanism, whose process can be "long" (running time) > on large scale systems as we are now seeing in HPC, if not correctly > implemented. > If the implementation of the standard does this, it can ensure good routing > and the "best" usage of message transfer mechanisms (architecture dependent) > to even terminate the application the soonest... > > Cheers. > > .Yves. > > PS: It seems that I nearly always forgot to answer on the list. Sorry... > > Le Monday 05 April 2010 16:53:57, vous avez écrit : > > Yves > > > > In my view, and I think in the view of those who developed the standard, an > > MPI program that ends in an MPI_Abort call is considered to have failed. > > > > If there is really a need for a mechanism to end an MPI program by a single > > task deciding that a correct answer has been achieved and whatever the > > other tasks are still doing can be considered expendable garbage, then > > perhaps the MPI Forum should be asked to consider a new function which does > > not carry the implication of job failure. > > > > I have never before heard anyone request such a mechanism but maybe there > > are many out there that just figure calling MPI_Abort is good enough. > > > > There is a current MPI Forum working on the 3.0 version of the MPI > > standard. Do you think they should be considering am MPI_Quit subroutine? > > > > > > Dick Treumann - MPI Team > > IBM Systems & Technology Group > > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > > Tele (845) 433-7846 Fax (845) 433-8363 > > > > > > > > > > From: Yves Caniou > > > > To: Richard Treumann/Poughkeepsie/IBM@IBMUS > > > > Date: 04/05/2010 10:38 AM > > > > Subject:Re: [OMPI users] Hide Abort output > > > > > > > > > > > > > > I am just saying that it is just about convenience. > > > > If a task in the application shows a divergence, it does not necessarily > > imply > > a failure of the application: It gives a result, non-convergence of the > > whole > > calculus for some initial condition for example. > > > > Another example: if your application is built as a graphe which ends by all > > > > tasks performing its own calculus: the first one finishing causes the > > application to end. Then, for simplicity, you can call MPI_Abort() to end > > the > > application -- even if I agree that it is not the proper way, since each > > task > > should call MPI_Finalize(). > > But in the proper way, the first finishing task should communicate to all > > of > > the other that they ha
Re: [OMPI users] Hide Abort output
I'm not sure I understand what your MPI_Quit function would do differently than MPI_Abort and/or MPI_Finalize...? On Apr 6, 2010, at 3:13 AM, Yves Caniou wrote: > I really understand the failure idea of the MPI_Abort() function, and it > clearly appeared in the recent mails. > > There is an evident advantage for me to have an MPI_Quit() function: > Having such a function would be great in the sens that someone would not have > to code the termination mechanism, whose process can be "long" (running time) > on large scale systems as we are now seeing in HPC, if not correctly > implemented. > If the implementation of the standard does this, it can ensure good routing > and the "best" usage of message transfer mechanisms (architecture dependent) > to even terminate the application the soonest... > > Cheers. > > .Yves. > > PS: It seems that I nearly always forgot to answer on the list. Sorry... > > Le Monday 05 April 2010 16:53:57, vous avez écrit : > > Yves > > > > In my view, and I think in the view of those who developed the standard, an > > MPI program that ends in an MPI_Abort call is considered to have failed. > > > > If there is really a need for a mechanism to end an MPI program by a single > > task deciding that a correct answer has been achieved and whatever the > > other tasks are still doing can be considered expendable garbage, then > > perhaps the MPI Forum should be asked to consider a new function which does > > not carry the implication of job failure. > > > > I have never before heard anyone request such a mechanism but maybe there > > are many out there that just figure calling MPI_Abort is good enough. > > > > There is a current MPI Forum working on the 3.0 version of the MPI > > standard. Do you think they should be considering am MPI_Quit subroutine? > > > > > > Dick Treumann - MPI Team > > IBM Systems & Technology Group > > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > > Tele (845) 433-7846 Fax (845) 433-8363 > > > > > > > > > > From: Yves Caniou > > > > To: Richard Treumann/Poughkeepsie/IBM@IBMUS > > > > Date: 04/05/2010 10:38 AM > > > > Subject:Re: [OMPI users] Hide Abort output > > > > > > > > > > > > > > I am just saying that it is just about convenience. > > > > If a task in the application shows a divergence, it does not necessarily > > imply > > a failure of the application: It gives a result, non-convergence of the > > whole > > calculus for some initial condition for example. > > > > Another example: if your application is built as a graphe which ends by all > > > > tasks performing its own calculus: the first one finishing causes the > > application to end. Then, for simplicity, you can call MPI_Abort() to end > > the > > application -- even if I agree that it is not the proper way, since each > > task > > should call MPI_Finalize(). > > But in the proper way, the first finishing task should communicate to all > > of > > the other that they have to finish, thus implying that you have coded some > > async receive in each task, with a correctly defined protocol, waiting for > > the termination message. > > > > I don't know if you consider this as a dirty trick and if there is other > > practical means to end properly the application in such cases (I am not a > > deep user of MPI), but at least, this should work very fine. > > > > .Yves. > > > > Le Monday 05 April 2010 15:45:47 Richard Treumann, vous avez écrit : > > > I do not really understand your argument. > > > > > > A correct MPI application ends when every task calls MPI_Finalize. I do > > > not know what a "join-node" is. > > > > > > MPI_Abort is for cases like getting an intermediate result that cannot > > > possible be right and deciding (within the application) to give up and > > > announce failure. > > > > > > > > > Dick Treumann - MPI Team > > > IBM Systems & Technology Group > > > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > > > Tele (845) 433-7846 Fax (845) 433-8363 > > > > > > > > > > > > > > > From: Yves Caniou > > > > > > To: Richard Treumann/Poughkeepsie/IBM@IBMUS > > > > > > Date: 04/05/2010 09:38 AM > > > > > > Subject:Re: [OMPI users] Hid
Re: [OMPI users] Hide Abort output
I really understand the failure idea of the MPI_Abort() function, and it clearly appeared in the recent mails. There is an evident advantage for me to have an MPI_Quit() function: Having such a function would be great in the sens that someone would not have to code the termination mechanism, whose process can be "long" (running time) on large scale systems as we are now seeing in HPC, if not correctly implemented. If the implementation of the standard does this, it can ensure good routing and the "best" usage of message transfer mechanisms (architecture dependent) to even terminate the application the soonest... Cheers. .Yves. PS: It seems that I nearly always forgot to answer on the list. Sorry... Le Monday 05 April 2010 16:53:57, vous avez écrit : > Yves > > In my view, and I think in the view of those who developed the standard, an > MPI program that ends in an MPI_Abort call is considered to have failed. > > If there is really a need for a mechanism to end an MPI program by a single > task deciding that a correct answer has been achieved and whatever the > other tasks are still doing can be considered expendable garbage, then > perhaps the MPI Forum should be asked to consider a new function which does > not carry the implication of job failure. > > I have never before heard anyone request such a mechanism but maybe there > are many out there that just figure calling MPI_Abort is good enough. > > There is a current MPI Forum working on the 3.0 version of the MPI > standard. Do you think they should be considering am MPI_Quit subroutine? > > > Dick Treumann - MPI Team > IBM Systems & Technology Group > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > Tele (845) 433-7846 Fax (845) 433-8363 > > > > > From: Yves Caniou > > To: Richard Treumann/Poughkeepsie/IBM@IBMUS > > Date: 04/05/2010 10:38 AM > > Subject:Re: [OMPI users] Hide Abort output > > > > > > > I am just saying that it is just about convenience. > > If a task in the application shows a divergence, it does not necessarily > imply > a failure of the application: It gives a result, non-convergence of the > whole > calculus for some initial condition for example. > > Another example: if your application is built as a graphe which ends by all > > tasks performing its own calculus: the first one finishing causes the > application to end. Then, for simplicity, you can call MPI_Abort() to end > the > application -- even if I agree that it is not the proper way, since each > task > should call MPI_Finalize(). > But in the proper way, the first finishing task should communicate to all > of > the other that they have to finish, thus implying that you have coded some > async receive in each task, with a correctly defined protocol, waiting for > the termination message. > > I don't know if you consider this as a dirty trick and if there is other > practical means to end properly the application in such cases (I am not a > deep user of MPI), but at least, this should work very fine. > > .Yves. > > Le Monday 05 April 2010 15:45:47 Richard Treumann, vous avez écrit : > > I do not really understand your argument. > > > > A correct MPI application ends when every task calls MPI_Finalize. I do > > not know what a "join-node" is. > > > > MPI_Abort is for cases like getting an intermediate result that cannot > > possible be right and deciding (within the application) to give up and > > announce failure. > > > > > > Dick Treumann - MPI Team > > IBM Systems & Technology Group > > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > > Tele (845) 433-7846 Fax (845) 433-8363 > > > > > > > > > > From: Yves Caniou > > > > To: Richard Treumann/Poughkeepsie/IBM@IBMUS > > > > Date: 04/05/2010 09:38 AM > > > > Subject:Re: [OMPI users] Hide Abort output > > > > > > > > > > > > > > In that case, if your application does not end by a join node, you code > > the > > > whole thing to make an async receive and the send that kills everyone in > > a > > > logn messages? > > > > .Yves. > > > > Le Monday 05 April 2010 15:27:33, vous avez écrit : > > > Yves > > > > > > If an application issued an MPI_Abort, it did not "end correctly". The > > > MPI_Abort call is intended for one thing only. The application has > > > recognized that something is so wrong that there is no point in > > > > continuing. &g
Re: [OMPI users] Hide Abort output
I sent that last message to quick. I was ignoring that MPI_Abort already
takes two args. I've been doing a lot of Perl the past few weeks, so I'm
in a perl state of mind.
I would say add a third arg to MPI_Abort for a programmer-defined error
string, but that would violate the standard, wouldn't it? Nevermind...
Prentice
Prentice Bisbal wrote:
> I would suggest that MPI_Abort take a string as an argument, and print
> out the that string when MPI_Abort is called. If a programmer wanted to
> NOT have an abort message, they could just omit the argument:
>
> MPI_Abort("Could not open file foo");
>
> or
>
> MPI_Abort();
>
> This would be similar to Perl's die command, where you can provide a
> string to printout when die is called.
>
>
> --
> Prentice
>
> David Singleton wrote:
>> Yes, Dick has isolated the issue - novice users often believe Open MPI
>> (not their application) had a problem. Anything along the lines he
>> suggests
>> can only help.
>>
>> David
>>
>> On 04/01/2010 01:12 AM, Richard Treumann wrote:
>>> I do not know what the OpenMPI message looks like or why people want to
>>> hide it. It should be phrased to avoid any implication of a problem with
>>> OpenMPI itself.
>>>
>>> How about something like this which:
>>>
>>> "The application has called MPI_Abort. The application is terminated by
>>> OpenMPI as the application demanded"
>>>
>>>
>>> Dick Treumann - MPI Team
>>> IBM Systems& Technology Group
>>> Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601
>>> Tele (845) 433-7846 Fax (845) 433-8363
>>>
>>>
>>>
>>>
>>>From: "Jeff Squyres (jsquyres)"
>>>
>>>To:,
>>>
>>>Date: 03/31/2010 06:43 AM
>>>
>>>Subject:Re: [OMPI users] Hide Abort output
>>>
>>>Sent by:users-boun...@open-mpi.org
>>>
>>>
>>>
>>>
>>>
>>>
>>> At present there is no such feature, but it should not be hard to add.
>>>
>>> Can you guys be a little more specific about exactly what you are seeing
>>> and exactly what you want to see? (And what version you're working
>>> with -
>>> I'll caveat my discussion that this may be a 1.5-and-forward thing)
>>>
>>> -jms
>>> Sent from my PDA. No type good.
>>>
>>> - Original Message -
>>> From: users-boun...@open-mpi.org
>>> To: Open MPI Users
>>> Sent: Wed Mar 31 05:38:48 2010
>>> Subject: Re: [OMPI users] Hide Abort output
>>>
>>>
>>> I have to say this is a very common issue for our users. They repeatedly
>>> report the long Open MPI MPI_Abort() message in help queries and fail to
>>> look for the application error message about the root cause. A short
>>> MPI_Abort() message that said "look elsewhere for the real error message"
>>> would be useful.
>>>
>>> Cheers,
>>> David
>>>
>>> On 03/31/2010 07:58 PM, Yves Caniou wrote:
>>>> Dear all,
>>>>
>>>> I am using the MPI_Abort() command in a MPI program.
>>>> I would like to not see the note explaining that the command caused Open
>>> MPI
>>>> to kill all the jobs and so on.
>>>> I thought that I could find a --mca parameter, but couldn't grep it. The
>>> only
>>>> ones deal with the delay and printing more information (the stack).
>>>>
>>>> Is there a mean to avoid the printing of the note (except the
>>>> 2>/dev/null
>>>> tips)? Or to delay this printing?
>>>>
>>>> Thank you.
>>>>
>>>> .Yves.
>>>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
--
Prentice Bisbal
Linux Software Support Specialist/System Administrator
School of Natural Sciences
Institute for Advanced Study
Princeton, NJ
Re: [OMPI users] Hide Abort output
I would suggest that MPI_Abort take a string as an argument, and print
out the that string when MPI_Abort is called. If a programmer wanted to
NOT have an abort message, they could just omit the argument:
MPI_Abort("Could not open file foo");
or
MPI_Abort();
This would be similar to Perl's die command, where you can provide a
string to printout when die is called.
--
Prentice
David Singleton wrote:
>
> Yes, Dick has isolated the issue - novice users often believe Open MPI
> (not their application) had a problem. Anything along the lines he
> suggests
> can only help.
>
> David
>
> On 04/01/2010 01:12 AM, Richard Treumann wrote:
>>
>> I do not know what the OpenMPI message looks like or why people want to
>> hide it. It should be phrased to avoid any implication of a problem with
>> OpenMPI itself.
>>
>> How about something like this which:
>>
>> "The application has called MPI_Abort. The application is terminated by
>> OpenMPI as the application demanded"
>>
>>
>> Dick Treumann - MPI Team
>> IBM Systems& Technology Group
>> Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601
>> Tele (845) 433-7846 Fax (845) 433-8363
>>
>>
>>
>>
>>From: "Jeff Squyres (jsquyres)"
>>
>>To:,
>>
>>Date: 03/31/2010 06:43 AM
>>
>>Subject:Re: [OMPI users] Hide Abort output
>>
>>Sent by:users-boun...@open-mpi.org
>>
>>
>>
>>
>>
>>
>> At present there is no such feature, but it should not be hard to add.
>>
>> Can you guys be a little more specific about exactly what you are seeing
>> and exactly what you want to see? (And what version you're working
>> with -
>> I'll caveat my discussion that this may be a 1.5-and-forward thing)
>>
>> -jms
>> Sent from my PDA. No type good.
>>
>> - Original Message -
>> From: users-boun...@open-mpi.org
>> To: Open MPI Users
>> Sent: Wed Mar 31 05:38:48 2010
>> Subject: Re: [OMPI users] Hide Abort output
>>
>>
>> I have to say this is a very common issue for our users. They repeatedly
>> report the long Open MPI MPI_Abort() message in help queries and fail to
>> look for the application error message about the root cause. A short
>> MPI_Abort() message that said "look elsewhere for the real error message"
>> would be useful.
>>
>> Cheers,
>> David
>>
>> On 03/31/2010 07:58 PM, Yves Caniou wrote:
>>> Dear all,
>>>
>>> I am using the MPI_Abort() command in a MPI program.
>>> I would like to not see the note explaining that the command caused Open
>> MPI
>>> to kill all the jobs and so on.
>>> I thought that I could find a --mca parameter, but couldn't grep it. The
>> only
>>> ones deal with the delay and printing more information (the stack).
>>>
>>> Is there a mean to avoid the printing of the note (except the
>>> 2>/dev/null
>>> tips)? Or to delay this printing?
>>>
>>> Thank you.
>>>
>>> .Yves.
>>>
>>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
Re: [OMPI users] Hide Abort output
Thanks Ralph Should have considered that. The assumption would be that anyone who is using the message suppression option is (or at least should be) wrapping the job launch in some script or other tool that records a non-0 RC as a job failure or raises a flag for them to say the job failed. A command line issue of something like mpirun usually gives no indication of the non-zero RC any well designed wrapper SHOULD catch it. Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 From: Ralph Castain To: Open MPI Users Date: 04/05/2010 09:41 AM Subject:Re: [OMPI users] Hide Abort output Sent by:users-boun...@open-mpi.org Not all distinctions - the exit status is non-zero. All that is suppressed are the messages telling you what the error -might- have been. On Apr 5, 2010, at 7:01 AM, Richard Treumann wrote: Why should any software system offer an option which lets the user hide all distinction between a run that succeeded and one that failed? Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Hide Abort output
Not all distinctions - the exit status is non-zero. All that is suppressed are the messages telling you what the error -might- have been. On Apr 5, 2010, at 7:01 AM, Richard Treumann wrote: > Why should any software system offer an option which lets the user hide all > distinction between a run that succeeded and one that failed? > > Dick Treumann - MPI Team > IBM Systems & Technology Group > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > Tele (845) 433-7846 Fax (845) 433-8363 > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Hide Abort output
Le Monday 05 April 2010 15:01:42 Richard Treumann, vous avez écrit : > Why should any software system offer an option which lets the user hide > all distinction between a run that succeeded and one that failed? > > Dick Treumann - MPI Team > IBM Systems & Technology Group > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > Tele (845) 433-7846 Fax (845) 433-8363 I don't understand how your question is related to mine, since in my case, the application ends correctly and I don't want any output. :? -- Yves Caniou Associate Professor at Université Lyon 1, Member of the team project INRIA GRAAL in the LIP ENS-Lyon, Délégation CNRS in Japan French Laboratory of Informatics (JFLI), * in Information Technology Center, The University of Tokyo, 2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan tel: +81-3-5841-0540 * in National Institute of Informatics 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan tel: +81-3-4212-2412 http://graal.ens-lyon.fr/~ycaniou/
Re: [OMPI users] Hide Abort output
Why should any software system offer an option which lets the user hide all distinction between a run that succeeded and one that failed? Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363
Re: [OMPI users] Hide Abort output
Testing found that I had missed a spot here, so we weren't fully suppressing messages (including MPI_Abort). So the corrected fix is in r22926, and will be included in tonight's tarball. I also made --quiet be a new MCA param orte_execute_quiet so you can put it in your environment instead of only on the cmd line. HTH Ralph On Apr 2, 2010, at 1:18 AM, Ralph Castain wrote: > Actually, a cmd line option to mpirun already existed for this purpose. > Unfortunately, it wasn't properly being respected, so even knowing about it > wouldn't have helped. > > I have fixed this as of r22925 on our developer's trunk and started the > script to generate a fresh nightly tarball. Give it a little time and then > you can find it on the web site: > > http://www.open-mpi.org/nightly/trunk/ > > Use the -q or --quiet option and the message will be suppressed. I will > request that this be included in the upcoming 1.4.2 and 1.5.0 releases. > > > On Apr 1, 2010, at 8:38 PM, Yves Caniou wrote: > >> For information, I use the debian-packaged OpenMPI 1.4.1. >> >> Cheers. >> >> .Yves. >> >> Le Wednesday 31 March 2010 12:41:34 Jeff Squyres (jsquyres), vous avez écrit >> : >>> At present there is no such feature, but it should not be hard to add. >>> >>> Can you guys be a little more specific about exactly what you are seeing >>> and exactly what you want to see? (And what version you're working with - >>> I'll caveat my discussion that this may be a 1.5-and-forward thing) >>> >>> -jms >>> Sent from my PDA. No type good. >>> >>> - Original Message - >>> From: users-boun...@open-mpi.org >>> To: Open MPI Users >>> Sent: Wed Mar 31 05:38:48 2010 >>> Subject: Re: [OMPI users] Hide Abort output >>> >>> >>> I have to say this is a very common issue for our users. They repeatedly >>> report the long Open MPI MPI_Abort() message in help queries and fail to >>> look for the application error message about the root cause. A short >>> MPI_Abort() message that said "look elsewhere for the real error message" >>> would be useful. >>> >>> Cheers, >>> David >>> >>> On 03/31/2010 07:58 PM, Yves Caniou wrote: >>>> Dear all, >>>> >>>> I am using the MPI_Abort() command in a MPI program. >>>> I would like to not see the note explaining that the command caused Open >>>> MPI to kill all the jobs and so on. >>>> I thought that I could find a --mca parameter, but couldn't grep it. The >>>> only ones deal with the delay and printing more information (the stack). >>>> >>>> Is there a mean to avoid the printing of the note (except the 2>/dev/null >>>> tips)? Or to delay this printing? >>>> >>>> Thank you. >>>> >>>> .Yves. >>> >>> ___ >>> users mailing list >>> us...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/users >> >> >> >> -- >> Yves Caniou >> Associate Professor at Université Lyon 1, >> Member of the team project INRIA GRAAL in the LIP ENS-Lyon, >> Délégation CNRS in Japan French Laboratory of Informatics (JFLI), >> * in Information Technology Center, The University of Tokyo, >> 2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan >> tel: +81-3-5841-0540 >> * in National Institute of Informatics >> 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan >> tel: +81-3-4212-2412 >> http://graal.ens-lyon.fr/~ycaniou/ >> >> ___ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users >
Re: [OMPI users] Hide Abort output
Actually, a cmd line option to mpirun already existed for this purpose. Unfortunately, it wasn't properly being respected, so even knowing about it wouldn't have helped. I have fixed this as of r22925 on our developer's trunk and started the script to generate a fresh nightly tarball. Give it a little time and then you can find it on the web site: http://www.open-mpi.org/nightly/trunk/ Use the -q or --quiet option and the message will be suppressed. I will request that this be included in the upcoming 1.4.2 and 1.5.0 releases. On Apr 1, 2010, at 8:38 PM, Yves Caniou wrote: > For information, I use the debian-packaged OpenMPI 1.4.1. > > Cheers. > > .Yves. > > Le Wednesday 31 March 2010 12:41:34 Jeff Squyres (jsquyres), vous avez écrit : >> At present there is no such feature, but it should not be hard to add. >> >> Can you guys be a little more specific about exactly what you are seeing >> and exactly what you want to see? (And what version you're working with - >> I'll caveat my discussion that this may be a 1.5-and-forward thing) >> >> -jms >> Sent from my PDA. No type good. >> >> - Original Message - >> From: users-boun...@open-mpi.org >> To: Open MPI Users >> Sent: Wed Mar 31 05:38:48 2010 >> Subject: Re: [OMPI users] Hide Abort output >> >> >> I have to say this is a very common issue for our users. They repeatedly >> report the long Open MPI MPI_Abort() message in help queries and fail to >> look for the application error message about the root cause. A short >> MPI_Abort() message that said "look elsewhere for the real error message" >> would be useful. >> >> Cheers, >> David >> >> On 03/31/2010 07:58 PM, Yves Caniou wrote: >>> Dear all, >>> >>> I am using the MPI_Abort() command in a MPI program. >>> I would like to not see the note explaining that the command caused Open >>> MPI to kill all the jobs and so on. >>> I thought that I could find a --mca parameter, but couldn't grep it. The >>> only ones deal with the delay and printing more information (the stack). >>> >>> Is there a mean to avoid the printing of the note (except the 2>/dev/null >>> tips)? Or to delay this printing? >>> >>> Thank you. >>> >>> .Yves. >> >> ___ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users > > > > -- > Yves Caniou > Associate Professor at Université Lyon 1, > Member of the team project INRIA GRAAL in the LIP ENS-Lyon, > Délégation CNRS in Japan French Laboratory of Informatics (JFLI), > * in Information Technology Center, The University of Tokyo, >2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan >tel: +81-3-5841-0540 > * in National Institute of Informatics >2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan >tel: +81-3-4212-2412 > http://graal.ens-lyon.fr/~ycaniou/ > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Hide Abort output
For information, I use the debian-packaged OpenMPI 1.4.1. Cheers. .Yves. Le Wednesday 31 March 2010 12:41:34 Jeff Squyres (jsquyres), vous avez écrit : > At present there is no such feature, but it should not be hard to add. > > Can you guys be a little more specific about exactly what you are seeing > and exactly what you want to see? (And what version you're working with - > I'll caveat my discussion that this may be a 1.5-and-forward thing) > > -jms > Sent from my PDA. No type good. > > - Original Message - > From: users-boun...@open-mpi.org > To: Open MPI Users > Sent: Wed Mar 31 05:38:48 2010 > Subject: Re: [OMPI users] Hide Abort output > > > I have to say this is a very common issue for our users. They repeatedly > report the long Open MPI MPI_Abort() message in help queries and fail to > look for the application error message about the root cause. A short > MPI_Abort() message that said "look elsewhere for the real error message" > would be useful. > > Cheers, > David > > On 03/31/2010 07:58 PM, Yves Caniou wrote: > > Dear all, > > > > I am using the MPI_Abort() command in a MPI program. > > I would like to not see the note explaining that the command caused Open > > MPI to kill all the jobs and so on. > > I thought that I could find a --mca parameter, but couldn't grep it. The > > only ones deal with the delay and printing more information (the stack). > > > > Is there a mean to avoid the printing of the note (except the 2>/dev/null > > tips)? Or to delay this printing? > > > > Thank you. > > > > .Yves. > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Yves Caniou Associate Professor at Université Lyon 1, Member of the team project INRIA GRAAL in the LIP ENS-Lyon, Délégation CNRS in Japan French Laboratory of Informatics (JFLI), * in Information Technology Center, The University of Tokyo, 2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan tel: +81-3-5841-0540 * in National Institute of Informatics 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan tel: +81-3-4212-2412 http://graal.ens-lyon.fr/~ycaniou/
Re: [OMPI users] Hide Abort output
Indeed, the small paragraph can be misunderstood, but that wasn't the goal of my question. The fact is that the message can appear in the middle of logs, which means post-treatments of outputs even if the end of the program is normal (the worflow does not end by a join node). I just want to be able to get rid of the message, maybe with a special option -- or no message by default, and the message appears when mpirun is invocated with a special debug option? .Yves. Le Thursday 01 April 2010 00:33:58 David Singleton, vous avez écrit : > Yes, Dick has isolated the issue - novice users often believe Open MPI > (not their application) had a problem. Anything along the lines he > suggests can only help. > > David > > On 04/01/2010 01:12 AM, Richard Treumann wrote: > > I do not know what the OpenMPI message looks like or why people want to > > hide it. It should be phrased to avoid any implication of a problem with > > OpenMPI itself. > > > > How about something like this which: > > > > "The application has called MPI_Abort. The application is terminated by > > OpenMPI as the application demanded" > > > > > > Dick Treumann - MPI Team > > IBM Systems& Technology Group > > Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 > > Tele (845) 433-7846 Fax (845) 433-8363 > > > > > > > > > >From: "Jeff Squyres (jsquyres)" > > > >To:, > > > >Date: 03/31/2010 06:43 AM > > > >Subject:Re: [OMPI users] Hide Abort output > > > >Sent by:users-boun...@open-mpi.org > > > > > > > > > > > > > > At present there is no such feature, but it should not be hard to add. > > > > Can you guys be a little more specific about exactly what you are seeing > > and exactly what you want to see? (And what version you're working with > > - I'll caveat my discussion that this may be a 1.5-and-forward thing) > > > > -jms > > Sent from my PDA. No type good. > > > > - Original Message - > > From: users-boun...@open-mpi.org > > To: Open MPI Users > > Sent: Wed Mar 31 05:38:48 2010 > > Subject: Re: [OMPI users] Hide Abort output > > > > > > I have to say this is a very common issue for our users. They repeatedly > > report the long Open MPI MPI_Abort() message in help queries and fail to > > look for the application error message about the root cause. A short > > MPI_Abort() message that said "look elsewhere for the real error message" > > would be useful. > > > > Cheers, > > David > > > > On 03/31/2010 07:58 PM, Yves Caniou wrote: > >> Dear all, > >> > >> I am using the MPI_Abort() command in a MPI program. > >> I would like to not see the note explaining that the command caused Open > > > > MPI > > > >> to kill all the jobs and so on. > >> I thought that I could find a --mca parameter, but couldn't grep it. The > > > > only > > > >> ones deal with the delay and printing more information (the stack). > >> > >> Is there a mean to avoid the printing of the note (except the > >> 2>/dev/null tips)? Or to delay this printing? > >> > >> Thank you. > >> > >> .Yves. > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Yves Caniou Associate Professor at Université Lyon 1, Member of the team project INRIA GRAAL in the LIP ENS-Lyon, Délégation CNRS in Japan French Laboratory of Informatics (JFLI), * in Information Technology Center, The University of Tokyo, 2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan tel: +81-3-5841-0540 * in National Institute of Informatics 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan tel: +81-3-4212-2412 http://graal.ens-lyon.fr/~ycaniou/
Re: [OMPI users] Hide Abort output
Yes, Dick has isolated the issue - novice users often believe Open MPI (not their application) had a problem. Anything along the lines he suggests can only help. David On 04/01/2010 01:12 AM, Richard Treumann wrote: I do not know what the OpenMPI message looks like or why people want to hide it. It should be phrased to avoid any implication of a problem with OpenMPI itself. How about something like this which: "The application has called MPI_Abort. The application is terminated by OpenMPI as the application demanded" Dick Treumann - MPI Team IBM Systems& Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 From: "Jeff Squyres (jsquyres)" To:, Date: 03/31/2010 06:43 AM Subject: Re: [OMPI users] Hide Abort output Sent by:users-boun...@open-mpi.org At present there is no such feature, but it should not be hard to add. Can you guys be a little more specific about exactly what you are seeing and exactly what you want to see? (And what version you're working with - I'll caveat my discussion that this may be a 1.5-and-forward thing) -jms Sent from my PDA. No type good. - Original Message - From: users-boun...@open-mpi.org To: Open MPI Users Sent: Wed Mar 31 05:38:48 2010 Subject: Re: [OMPI users] Hide Abort output I have to say this is a very common issue for our users. They repeatedly report the long Open MPI MPI_Abort() message in help queries and fail to look for the application error message about the root cause. A short MPI_Abort() message that said "look elsewhere for the real error message" would be useful. Cheers, David On 03/31/2010 07:58 PM, Yves Caniou wrote: Dear all, I am using the MPI_Abort() command in a MPI program. I would like to not see the note explaining that the command caused Open MPI to kill all the jobs and so on. I thought that I could find a --mca parameter, but couldn't grep it. The only ones deal with the delay and printing more information (the stack). Is there a mean to avoid the printing of the note (except the 2>/dev/null tips)? Or to delay this printing? Thank you. .Yves.
Re: [OMPI users] Hide Abort output
I do not know what the OpenMPI message looks like or why people want to hide it. It should be phrased to avoid any implication of a problem with OpenMPI itself. How about something like this which: "The application has called MPI_Abort. The application is terminated by OpenMPI as the application demanded" Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 From: "Jeff Squyres (jsquyres)" To: , Date: 03/31/2010 06:43 AM Subject: Re: [OMPI users] Hide Abort output Sent by:users-boun...@open-mpi.org At present there is no such feature, but it should not be hard to add. Can you guys be a little more specific about exactly what you are seeing and exactly what you want to see? (And what version you're working with - I'll caveat my discussion that this may be a 1.5-and-forward thing) -jms Sent from my PDA. No type good. - Original Message - From: users-boun...@open-mpi.org To: Open MPI Users Sent: Wed Mar 31 05:38:48 2010 Subject: Re: [OMPI users] Hide Abort output I have to say this is a very common issue for our users. They repeatedly report the long Open MPI MPI_Abort() message in help queries and fail to look for the application error message about the root cause. A short MPI_Abort() message that said "look elsewhere for the real error message" would be useful. Cheers, David On 03/31/2010 07:58 PM, Yves Caniou wrote: > Dear all, > > I am using the MPI_Abort() command in a MPI program. > I would like to not see the note explaining that the command caused Open MPI > to kill all the jobs and so on. > I thought that I could find a --mca parameter, but couldn't grep it. The only > ones deal with the delay and printing more information (the stack). > > Is there a mean to avoid the printing of the note (except the 2>/dev/null > tips)? Or to delay this printing? > > Thank you. > > .Yves. > ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Hide Abort output
At present there is no such feature, but it should not be hard to add. Can you guys be a little more specific about exactly what you are seeing and exactly what you want to see? (And what version you're working with - I'll caveat my discussion that this may be a 1.5-and-forward thing) -jms Sent from my PDA. No type good. - Original Message - From: users-boun...@open-mpi.org To: Open MPI Users Sent: Wed Mar 31 05:38:48 2010 Subject: Re: [OMPI users] Hide Abort output I have to say this is a very common issue for our users. They repeatedly report the long Open MPI MPI_Abort() message in help queries and fail to look for the application error message about the root cause. A short MPI_Abort() message that said "look elsewhere for the real error message" would be useful. Cheers, David On 03/31/2010 07:58 PM, Yves Caniou wrote: > Dear all, > > I am using the MPI_Abort() command in a MPI program. > I would like to not see the note explaining that the command caused Open MPI > to kill all the jobs and so on. > I thought that I could find a --mca parameter, but couldn't grep it. The only > ones deal with the delay and printing more information (the stack). > > Is there a mean to avoid the printing of the note (except the 2>/dev/null > tips)? Or to delay this printing? > > Thank you. > > .Yves. > ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Hide Abort output
I have to say this is a very common issue for our users. They repeatedly report the long Open MPI MPI_Abort() message in help queries and fail to look for the application error message about the root cause. A short MPI_Abort() message that said "look elsewhere for the real error message" would be useful. Cheers, David On 03/31/2010 07:58 PM, Yves Caniou wrote: Dear all, I am using the MPI_Abort() command in a MPI program. I would like to not see the note explaining that the command caused Open MPI to kill all the jobs and so on. I thought that I could find a --mca parameter, but couldn't grep it. The only ones deal with the delay and printing more information (the stack). Is there a mean to avoid the printing of the note (except the 2>/dev/null tips)? Or to delay this printing? Thank you. .Yves.
[OMPI users] Hide Abort output
Dear all, I am using the MPI_Abort() command in a MPI program. I would like to not see the note explaining that the command caused Open MPI to kill all the jobs and so on. I thought that I could find a --mca parameter, but couldn't grep it. The only ones deal with the delay and printing more information (the stack). Is there a mean to avoid the printing of the note (except the 2>/dev/null tips)? Or to delay this printing? Thank you. .Yves. -- Yves Caniou Associate Professor at Université Lyon 1, Member of the team project INRIA GRAAL in the LIP ENS-Lyon, Délégation CNRS in Japan French Laboratory of Informatics (JFLI), * in Information Technology Center, The University of Tokyo, 2-11-16 Yayoi, Bunkyo-ku, Tokyo 113-8658, Japan tel: +81-3-5841-0540 * in National Institute of Informatics 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo 101-8430, Japan tel: +81-3-4212-2412 http://graal.ens-lyon.fr/~ycaniou/
