It seems a wrong count or a lost race, it is checking too late and the
file and the /tmp/ompi.LAPTOP-82F08ILC.197609 tree is already close and gone
315 30730897 [main] orterun 93 close: close(21)
310 30731207 [main] orterun 93 fhandler_base::close: closing
It is the latter one it is complaining about:
> /tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo
I have no idea why it is complaining.
> On Feb 3, 2020, at 2:03 PM, Marco Atzeri via devel
> wrote:
>
> Am 03.02.2020 um 18:15 schrieb Ralph Castain via devel:
>> Hi Marco
>>
Am 03.02.2020 um 18:15 schrieb Ralph Castain via devel:
Hi Marco
mpirun isn't trying to run a debugger. It is opening a fifo pipe in case
a debugger later wishes to attach to the running job - it is used by an
MPIR-based debugger to let mpirun know that it is attaching. My guess is
that the
Hi Marco
mpirun isn't trying to run a debugger. It is opening a fifo pipe in case a
debugger later wishes to attach to the running job - it is used by an
MPIR-based debugger to let mpirun know that it is attaching. My guess is that
the code is attempting to create the fifo in an unacceptable
Am 02.02.2020 um 14:16 schrieb Jeff Squyres (jsquyres):
On Feb 2, 2020, at 2:17 AM, Marco Atzeri via devel
wrote:
not a new issue as it was also in 3.1.5. what is causing the
last line of warning ?
And why a simple run should try to run a debugger ?
$ mpirun -n 4 ./hello_c
...
Hello, world,
On Feb 2, 2020, at 2:17 AM, Marco Atzeri via devel
wrote:
>
> not a new issue as it was also in 3.1.5. what is causing the
> last line of warning ?
> And why a simple run should try to run a debugger ?
>
> $ mpirun -n 4 ./hello_c
> ...
> Hello, world, I am 3 of 4, (Open MPI v3.1.6rc2, package:
