On Dec 8, 2008, at 8:03 AM, Number Cruncher wrote:
> I notice that bug ticket #954 https://svn.open-mpi.org/trac/ompi/ticket/954
> has the very issue I'm encountering: I want to know when mpirun
> fails because of a missing executable during some automated tests.
> At the moment, nearly 2 years after the bug was reported, orterun/
> mpirun still returns a zero exit status even when it can't find the
> I note that this was "fixed" 20 months ago in "1.3". But there have
> been 1.2.1, 1.2.2, .... 1.2.8 since this and still no 1.3!
> So here's my appeal for a 1.2 bugfix....
We feel your pain. Trust me, we do. :-(
We really wanted to get v1.3 out a long time ago, but we specifically
decided that 1.3 would be a feature-driven release, not a schedule-
driven release. Unfortunately, it has taken a *lot* longer to
implement the features that we wanted than we anticipated. Doh.
The good news is that we're darn close to releasing v1.3. We actually
would have released earlier this week but a blocker bug showed up
literally at the last second that we *need* to fix before releasing
v1.3 (George still hasn't filed a ticket about it, but the bug
exists). Per http://www.open-mpi.org/community/lists/devel/2008/12/5029.php
, Brad Benton (our release manager) announced that if we can get a fix
in the next day or so, we'll still release v1.3 this year.
If the fix is more complicated, because most of us will be at the MPI
Forum meeting next week (meaning: we won't be able to be working on
code and regression testing necessary for a release) and then 2 weeks
of holidays following that, it's extremely unlikely that we'll release
v1.3 before January.
So cross your fingers and hope that we were all good enough that Santa
will give us an early Christmas present this year...