Re: [OMPI devel] RFC: Resilient ORTE

Committed in r24815. On Thursday, June 23, 2011 at 4:19 PM, Ralph Castain wrote: > > On Jun 23, 2011, at 2:14 PM, Wesley Bland wrote: > > Maybe before the ORTED saw the signal, it detected a communication failure > > and reacted to that. > > Quite possible. However, remember that procs local

Re: [OMPI devel] Compiling problem in trunk?

Hello, * Xin He wrote on Thu, Jun 23, 2011 at 01:23:53PM CEST: > make[3]: Entering directory `/home/ehhexxn/git/ompi/ompi/include' > FC mpif90-ext.lo > libtool: compile: unrecognized option `-c' > libtool: compile: Try `libtool --help' for more information. > make[3]: *** [mpif90-ext.lo]

Re: [OMPI devel] RFC: Resilient ORTE

Ga - what a rookie mistake :) I tested the patched test and it works as advertised for the small scale tests I used before. So I'm good with this going in today. Thanks, Josh On Thu, Jun 23, 2011 at 3:34 PM, Wesley Bland wrote: > Right. Sorry I misspoke. > > On Thursday,

Re: [OMPI devel] RFC: Resilient ORTE

Right. Sorry I misspoke. On Thursday, June 23, 2011 at 3:32 PM, Ralph Castain wrote: > Ummm...just to clarify. There are no threads in ORTE, so it wasn't a problem > of "not giving up the thread". The problem was that Josh's test never called > progress. It would have been equally okay to

Re: [OMPI devel] RFC: Resilient ORTE

Ummm...just to clarify. There are no threads in ORTE, so it wasn't a problem of "not giving up the thread". The problem was that Josh's test never called progress. It would have been equally okay to simply call "opal_event_dispatch" while waiting for the callback. All applications have to

Re: [OMPI devel] RFC: Resilient ORTE

Josh, There were a couple of bugs that I cleared up in my most recent checkin, but I also needed to modify your test. The callback for the application layer errmgr actually occurs in the application layer. Your test was never giving up the thread to the ORTE application event loop to receive

Re: [OMPI devel] Compiling problem in trunk?

Xin -- Can you provide more details on exactly what part of the build is failing? None of the rest of us are seeing the problem. When you svn up'ed, did you re-run autogen.pl / configure? On Jun 23, 2011, at 9:04 AM, Xin He wrote: > Thanks for the tips about configuration. Yet the build

Re: [OMPI devel] RFC: Resilient ORTE

So I finally got a chance to test the branch this morning. I cannot get it to work. Maybe I'm doing some wrong, missing some MCA parameter? - [jjhursey@smoky-login1 resilient-orte] hg summary parent: 2:c550cf6ed6a2 tip Newest version. Synced with trunk r24785. branch:

Re: [OMPI devel] RFC: Resilient ORTE

Last reminder (I hope). RFC goes in a COB today. Wesley

Re: [OMPI devel] Compiling problem in trunk?

FWIW: I haven't seen this problem on Mac or Linux since your commit, but I build with fortran disabled. Still, he claims to be seeing it even with disable-fortran, so I should have seen it too On Jun 23, 2011, at 7:38 AM, Josh Hursey wrote: > Yea that is where the problem is showing up,

Re: [OMPI devel] Compiling problem in trunk?

Thanks for the tips about configuration. Yet the build still failed. Anyway, I managed to roll back to an earlier version and successfully installed :) /Xin On 06/23/2011 01:26 PM, Jeff Squyres wrote: I don't believe we have changed anything in the trunk w.r.t. the Fortran 90 stuff (there's

Re: [OMPI devel] Compiling problem in trunk?

I don't believe we have changed anything in the trunk w.r.t. the Fortran 90 stuff (there's stuff off in a branch waiting to come in, but I don't think it has come in). Since you're primarily working on a new BTL, you might want to speed up your configure/build process by disabling Fortran and

[OMPI devel] Compiling problem in trunk?

Hi, as I compiled the sources from "trunk". I got these error messages when doing make: [blablabla...] make all-am make[3]: Entering directory `/home/ehhexxn/git/ompi/ompi/include' FC mpif90-ext.lo libtool: compile: unrecognized option `-c' libtool: compile: Try `libtool --help' for