Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

2022-01-09 Thread Marco Atzeri via devel
On 10.01.2022 06:50, Marco Atzeri wrote: On 09.01.2022 15:54, Ralph Castain via devel wrote: Hi Marco Try the patch here (for the prrte 3rd-party subdirectory): https://github.com/openpmix/prrte/pull/1173 Ralph Thanks Ralph, I will do on the next build as I need still to test the

Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

2022-01-09 Thread Marco Atzeri via devel
On 09.01.2022 15:54, Ralph Castain via devel wrote: Hi Marco Try the patch here (for the prrte 3rd-party subdirectory): https://github.com/openpmix/prrte/pull/1173 Ralph Thanks Ralph, I will do on the next build as I need still to test the current build. To complete the build I also

Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

2022-01-09 Thread Marco Atzeri via devel
On 01.01.2022 20:07, Barrett, Brian wrote: Marco - There are some patches that haven't made it to the 5.0 branch to make this behavior better. I didn't get a chance to back port them before the holiday break, but they will be in the next RC. That said, the issue below is a warning, not an

Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

2021-12-22 Thread Marco Atzeri via devel
On 18.10.2021 20:39, Austen W Lauria via devel wrote: The second release candidate for the Open MPI v5.0.0 release is posted at: https://www.open-mpi.org/software/ompi/v5.0/ Question: there is a easy way to configure and build the 3rd party

Re: [OMPI devel] Announcing Open MPI v4.0.4rc2

2020-06-06 Thread Marco Atzeri via devel
On 06.06.2020 10:37, Ralph Castain via devel wrote: I would have hoped that the added protections we put into PMIx would have resolved ds12 as well as ds21, but it is possible those changes didn't get into OMPI v4.0.x. Regardless, I think you should be just fine using the gds/hash component

Re: [OMPI devel] Announcing Open MPI v4.0.4rc2

2020-06-05 Thread Marco Atzeri via devel
On 05.06.2020 22:29, Marco Atzeri wrote: On 01.06.2020 20:26, Geoffrey Paulsen via devel wrote: Open MPI v4.0.4rc2 is now available for download and test at: sso_last: https://www.open-mpi.org/software/ompi/v4.0/ It builds on Cygwin64 bit, and this time it runs, but the PMIX is throwing

Re: [OMPI devel] Announcing Open MPI v4.0.4rc2

2020-06-05 Thread Marco Atzeri via devel
On 01.06.2020 20:26, Geoffrey Paulsen via devel wrote: Open MPI v4.0.4rc2 is now available for download and test at: sso_last: https://www.open-mpi.org/software/ompi/v4.0/ It builds on Cygwin64 bit, and this time it runs, but the PMIX is throwing some errors: $ mpirun -n 4 ./hello_c.exe

Re: [OMPI devel] Please test Open MPI v4.0.4rc1

2020-05-10 Thread Marco Atzeri via devel
Am 09.05.2020 um 17:18 schrieb Howard Pritchard via devel: Open MPI v4.0.4rc1 has been posted to https://www.open-mpi.org/software/ompi/v4.0/ 4.0.4 -- May, 2020 --- - Fix an ABI compatibility issue with the Fortran 2008 bindings. Thanks to Alastair McKinstry for

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-03 Thread Marco Atzeri via devel
Am 04.02.2020 um 04:17 schrieb Ralph Castain via devel: 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

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-03 Thread Marco Atzeri via devel
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

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-02 Thread Marco Atzeri via devel
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

Re: [OMPI devel] v3.0.6rc2 and v3.1.6rc2 available for testing

2020-02-01 Thread Marco Atzeri via devel
Am 30.01.2020 um 21:39 schrieb Jeff Squyres (jsquyres) via devel: Minor updates since rc1: 3.0.6rc2 and 3.1.6rc2: - Fix run-time linker issues with OMPIO on newer Linux distros. 3.1.6rc2 only: - Fix issue with zero-length blockLength in MPI_TYPE_INDEXED. Please test:

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

2020-01-01 Thread Marco Atzeri via devel
message by simply adding "gds = ^ds21" to your default MCA param file (the pmix one - should be named pmix-mca-params.conf). Artem - any advice here? On Dec 25, 2019, at 9:56 AM, Marco Atzeri via devel wrote: I have no multinode around for testing I will need to setup one for tes

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

2019-12-25 Thread Marco Atzeri via devel
, though, since the job seemed to run ok. Are you able to run multi-node jobs ok? On Dec 22, 2019, at 1:20 AM, Marco Atzeri via devel wrote: Hi Developers, Cygwin 64bit, openmpi-3.1.5-1 testing the cygwin package before releasing it I see a never seen before spurious error messages that do

[OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

2019-12-21 Thread Marco Atzeri via devel
Hi Developers, Cygwin 64bit, openmpi-3.1.5-1 testing the cygwin package before releasing it I see a never seen before spurious error messages that do not seem about error at all: $ mpirun -n 4 ./hello_c.exe [LAPTOP-82F08ILC:02395] PMIX ERROR: INIT in file