Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-14 Thread Ralph Castain
Think I got this fixed on the trunk - see https://svn.open-mpi.org/trac/ompi/ticket/4393 On Mar 13, 2014, at 8:51 PM, tmish...@jcity.maeda.co.jp wrote: > > > I happened to misspell a hostname, then it hanged. > > [mishima@manage ~]$ mpirun -np 6 -host node05,nod06 > ~/mis/openmpi/demos/mypro

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-13 Thread tmishima
I happened to misspell a hostname, then it hanged. [mishima@manage ~]$ mpirun -np 6 -host node05,nod06 ~/mis/openmpi/demos/myprog nod06: Unknown host mpirun: abort is already in progress...hit ctrl-c again to forcibly terminate Tetsuya > No problem - we appreciate you taking the time to confir

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-13 Thread Ralph Castain
No problem - we appreciate you taking the time to confirm. Jeff encountered something late today, so we may indeed still have a lingering problem. :-( Will keep you posted Ralph On Mar 13, 2014, at 5:08 PM, tmish...@jcity.maeda.co.jp wrote: > > > Hi Ralph, I'm late to your release again due

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-13 Thread tmishima
Hi Ralph, I'm late to your release again due to TD. At that time, I manually applied #4386 and #4383 to 1.7 branch - namely openmpi-1.7.5rc2, and did the check. I might have made some mistake. Now, I found openmpi-1.7.5rc3 had just released and confirmed it worked fine, thanks. Tetsuya > It's

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-13 Thread Ralph Castain
It's okay - we thought we had it fixed, but not for that scenario. On Mar 12, 2014, at 9:02 PM, tmish...@jcity.maeda.co.jp wrote: > > > Sorry for disturbing, please keep going ... > > Tetsuya > >> Yes, I know - I am just finishing the fix now. >> >> On Mar 12, 2014, at 8:48 PM, tmish...@jcit

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-13 Thread tmishima
Sorry for disturbing, please keep going ... Tetsuya > Yes, I know - I am just finishing the fix now. > > On Mar 12, 2014, at 8:48 PM, tmish...@jcity.maeda.co.jp wrote: > > > > > > > Hi Ralph, this problem is not fixed completely by today's latest > > ticket #4383, I guess ... > > > > https://sv

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-12 Thread Ralph Castain
Yes, I know - I am just finishing the fix now. On Mar 12, 2014, at 8:48 PM, tmish...@jcity.maeda.co.jp wrote: > > > Hi Ralph, this problem is not fixed completely by today's latest > ticket #4383, I guess ... > > https://svn.open-mpi.org/trac/ompi/ticket/4383 > > For example, in case of retur

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-12 Thread tmishima
Hi Ralph, this problem is not fixed completely by today's latest ticket #4383, I guess ... https://svn.open-mpi.org/trac/ompi/ticket/4383 For example, in case of returing with ORTE_ERR_SILENT from the line 514 in rmaps_rr_mapper.c file, the problem still occurs. I executed the job under the unm

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-12 Thread tmishima
Thanks, Jeff. I really understood the situation. Tetsuya > This all seems to be a side-effect of r30942 -- see: > > https://svn.open-mpi.org/trac/ompi/ticket/4365 > > > On Mar 12, 2014, at 5:13 AM, wrote: > > > > > > > Hi Ralph, > > > > I installed openmpi-1.7.5rc2 and applied r31019 to it. >

Re: [OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-12 Thread Jeff Squyres (jsquyres)
This all seems to be a side-effect of r30942 -- see: https://svn.open-mpi.org/trac/ompi/ticket/4365 On Mar 12, 2014, at 5:13 AM, wrote: > > > Hi Ralph, > > I installed openmpi-1.7.5rc2 and applied r31019 to it. > As far as I confirmed, rmaps framework worked fine. > > However, by chanc

[OMPI users] ctrl+c to abort a job with openmpi-1.7.5rc2

2014-03-12 Thread tmishima
Hi Ralph, I installed openmpi-1.7.5rc2 and applied r31019 to it. As far as I confirmed, rmaps framework worked fine. However, by chance, I noticed that single ctrl+c typing could not terminate a running job. Twice typing was necessary. Is this your expected behavior? I didn't use ctrl+c to abo