Your message dated Mon, 09 Apr 2012 08:48:32 -0400
with message-id <[email protected]>
and subject line Re: Bug#369287: closed by Camm Maguire
<[email protected]> (mpirun.lam: stdout from remote nodes doesn't make it
to the tty)
has caused the Debian Bug report #369287,
regarding mpirun.lam: stdout from remote nodes doesn't make it to the tty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
369287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369287
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lam-runtime
Version: 7.1.1-3
Running the hello program from /usr/share/doc/lam4-dev/examples/main/hello/
with
mpirun C ./hello
on a multi-node boot schema, I only see output from the processors on
the local node. This is unexpected.
If instead I run
mpirun C ./hello | cat
or
mpirun C ./hello > hello.out
I see the output from all processors on all nodes.
I've only tested this on amd64; no idea whether this behaviour occurs on
other platforms.
--- End Message ---
--- Begin Message ---
Greetings, and thanks!
Sergio Gelato <[email protected]> writes:
> * Camm Maguire [2012-04-06 14:01:32 -0400]:
>> reopen 369287
>
> Why? I exaplicitly did not ask you to do that.
>
Sorry, I thought there was an indication in HISTORY which needed followup.
>> > That said, I'm not going to reopen at this time because I'm no longer
>> > interested in verifying that the problem persists. Our clusters no longer
>> > run Debian, and our users have mostly moved on to OpenMPI (we don't even
>> > install lam4-dev any more). It is conceivable, though not exactly obvious
>> > from reading the HISTORY file, that this bug was fixed in 7.1.2. Had you
>>
>> to what entry are you referring?
>
> My wording may have been unfortunate. What I meant to say was that I could
> not find any entry in the HISTORY file that obviously covered this issue,
> but that it does not follow that the problem still exists. Only testing,
> or an understanding of the root cause of the problem, would help settle that.
>
OK
>> > written that you tried and failed to reproduce the problem in the latest
>> > release, that would have been a more convincing reason for closing the bug.
>> >
>>
>> Alas, I no longer have cluster access, and never did to an amd64
>> cluster.
>
> It can't be very easy to maintain this package without access to a suitable
> test environment.
>
> I've just set up a pair of virtual machines, running squeeze (actually two
> pairs, one i386 and one amd64), tried *and failed* to reproduce the problem.
> So either it's fixed or its nature is such that it no longer manifests
> itself in the same way. In either case this bug report can be closed since
> the bug has only been observed in releases of Debian that are no longer
> supported.
>
I really appreciate your effort here. Thank you so much! I agree this
can be now closed.
Take care,
--
Camm Maguire [email protected]
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
--- End Message ---
