Gilles: Can you submit a PR to fix these 2 places?
Thanks!
> On Sep 11, 2018, at 9:10 AM, emre brookes wrote:
>
> Gilles Gouaillardet wrote:
>> It seems I got it wrong :-(
> Ah, you've joined the rest of us :)
>>
>> Can you please give the attached patch a try ?
>>
> Working with a git clone
Gilles Gouaillardet wrote:
It seems I got it wrong :-(
Ah, you've joined the rest of us :)
Can you please give the attached patch a try ?
Working with a git clone of 3.1.x, patch applied
$ /src/ompi-3.1.x/bin/mpicxx test.cpp
$ /src/ompi-3.1.x/bin/mpirun a.out > stdout
--
Looks like there is a place in orte/mca/state/state_base_fns.c:850 that also
outputs to orte_clean_output instead of using show_help. Outside of those two
places, everything else seems to go to show_help.
> On Sep 10, 2018, at 8:58 PM, Gilles Gouaillardet wrote:
>
> It seems I got it wrong :-
It seems I got it wrong :-(
Can you please give the attached patch a try ?
FWIW, an other option would be to opal_output(orte_help_output, ...) but
we would have to make orte_help_output "public first.
Cheers,
Gilles
On 9/11/2018 11:14 AM, emre brookes wrote:
Gilles Gouaillardet wro
Gilles Gouaillardet wrote:
I investigated a this a bit and found that the (latest ?) v3 branches
have the expected behavior
(e.g. the error messages is sent to stderr)
Since it is very unlikely Open MPI 2.1 will ever be updated, I can
simply encourage you to upgrade to a newer Open MPI versi
I investigated a this a bit and found that the (latest ?) v3 branches
have the expected behavior
(e.g. the error messages is sent to stderr)
Since it is very unlikely Open MPI 2.1 will ever be updated, I can
simply encourage you to upgrade to a newer Open MPI version.
Latest fully supported
I’m not sure why this would be happening. These error outputs go through the
“show_help” functionality, and we specifically target it at stderr:
/* create an output stream for us */
OBJ_CONSTRUCT(&lds, opal_output_stream_t);
lds.lds_want_stderr = true;
orte_help_output = opal_outp
Thanks Gilles,
My goal is to separate openmpi errors from the stdout of the MPI program
itself so that errors can be identified externally (in particular in an
external framework running MPI jobs from various developers).
My not so "well written MPI program" was doing this:
MPI_Finalize();
Open MPI should likely write this message on stderr, I will have a look
at that.
That being said, and though I have no intention to dodge the question,
this case should not happen.
A well written (MPI) program should either exit(0) or have main() return
0, so this scenario
(e.g. all MPI t
emre brookes wrote:
George Reeke wrote:
On Tue, 2018-09-04 at 16:08 -0500, emre brookes wrote:
Is there some setting to turn off the extra messages generated by
openmpi ?
--
which strangely goes to stdout and not stderr.
I would intuitively expect error or notice messages to go to std
George Reeke wrote:
On Tue, 2018-09-04 at 16:08 -0500, emre brookes wrote:
Is there some setting to turn off the extra messages generated by openmpi ?
--
which strangely goes to stdout and not stderr.
I would intuitively expect error or notice messages to go to stderr.
Is there a way t
On Tue, 2018-09-04 at 16:08 -0500, emre brookes wrote:
> Is there some setting to turn off the extra messages generated by openmpi ?
--
> which strangely goes to stdout and not stderr.
> I would intuitively expect error or notice messages to go to stderr.
> Is there a way to redirect these
12 matches
Mail list logo
