commit not fix it for you?
>>>
>>>
>>> https://github.com/open-mpi/ompi/commit/7de01b347cd13544439b4eae86607a535c32489c
>>>
>>> If it didn't, then we might as well revert that commit and PR 1351 until
>>> it's fixed properly.
>>>
might as well revert that commit and PR 1351
until it's fixed properly.
-Original Message-
From: Ralph Castain
Reply: Open MPI Developers
Date: February 17, 2016 at 3:29:32 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] Trunk is broken
Probably should - looks like this
mpi/ompi/commit/7de01b347cd13544439b4eae86607a535c32489c
If it didn't, then we might as well revert that commit and PR 1351 until it's
fixed properly.
-Original Message-
From: Ralph Castain
Reply: Open MPI Developers
Date: February 17, 2016 at 3:29:32 PM
To: Open MPI Developers
Subject: Re: [OM
-Original Message-
From: Ralph Castain
Reply: Open MPI Developers
Date: February 17, 2016 at 3:29:32 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] Trunk is broken
> Probably should - looks like this may take more thought and probably will be
> handled in
> discussions next
Probably should - looks like this may take more thought and probably will be
handled in discussions next week
> On Feb 17, 2016, at 11:26 AM, Howard Pritchard wrote:
>
> Hi Folks,
>
> Should we revert PR 1351 till there is a fix?
>
> Howard
>
>
> 2016-02-17 11:34 GMT-07:00 Ralph Castain <
Hi Folks,
Should we revert PR 1351 till there is a fix?
Howard
2016-02-17 11:34 GMT-07:00 Ralph Castain :
> FWIW: I wouldn’t have seen that because I don’t have IB on my system.
>
> On Feb 17, 2016, at 10:11 AM, Nysal Jan K A wrote:
>
> So this seems to be still broken.
>
> mca_btl_openib.so:
FWIW: I wouldn’t have seen that because I don’t have IB on my system.
> On Feb 17, 2016, at 10:11 AM, Nysal Jan K A wrote:
>
> So this seems to be still broken.
>
> mca_btl_openib.so: undefined symbol: opal_memory_linux_malloc_set_alignment
>
> I built with "--with-memory-manager=none"
>
> Re
So this seems to be still broken.
mca_btl_openib.so: undefined symbol: opal_memory_linux_malloc_set_alignment
I built with "--with-memory-manager=none"
Regards
--Nysal
On Tue, Feb 16, 2016 at 10:19 AM, Ralph Castain wrote:
> It is very easy to reproduce - configure with:
> enable_mem_debug=no
It is very easy to reproduce - configure with:
enable_mem_debug=no
enable_mem_profile=no
enable_memchecker=no
with_memory_manager=no
I’m not sure which of those is required. However, your assertion is incorrect.
The person who introduced the original violation went to great lengths to
ensure it
Ralph,
this is being discussed at https://github.com/open-mpi/ompi/pull/1351
btw, how do you get this warning ? i do not see it.
fwiw, the abstraction violation was kind of already here, so i am
surprised it pops up now only
Cheers,
Gilles
On 2/16/2016 1:17 PM, Ralph Castain wrote:
Looks l
Looks like someone broke the master build on Linux:
../../../ompi/.libs/libmpi.so: undefined reference to
`opal_memory_linux_malloc_init_hook'
I suspect it was a hard-coded reference to some component’s variable?
Ralph
Hello!
Thanks, updated svn:ingore on oshmem folder in rev 31336.
On Tue, Apr 8, 2014 at 4:36 PM, Jeff Squyres (jsquyres)
wrote:
> Please also update the svn:ignore properties in the oshmem tree.
>
>
> On Apr 8, 2014, at 6:52 AM, Mike Dubman wrote:
>
> > thanks
> > fixed here: r31334
> >
> >
>
Please also update the svn:ignore properties in the oshmem tree.
On Apr 8, 2014, at 6:52 AM, Mike Dubman wrote:
> thanks
> fixed here: r31334
>
>
> On Tue, Apr 8, 2014 at 6:03 AM, Ralph Castain wrote:
> On Linux, with oshmem enabled:
>
> pinit_f.c:26:2: warning: #ident is a GCC extension
>
thanks
fixed here: r31334
On Tue, Apr 8, 2014 at 6:03 AM, Ralph Castain wrote:
> On Linux, with oshmem enabled:
>
> pinit_f.c:26:2: warning: #ident is a GCC extension
> pshmem_init.c:31: warning: no previous prototype for 'pstart_pes'
> pshmem_align.c:25: warning: no previous prototype for 'psh
And the svn ignore properties are missing:
? oshmem/shmem/c/profile/pshmem_addr_accessible.c
? oshmem/shmem/c/profile/pshmem_clear_lock.c
? oshmem/shmem/c/profile/pshmem_set_cache_line_inv.c
? oshmem/shmem/c/profile/pshmem_broadcast.c
? oshmem/shmem/c/profile/pshmem_w
On Linux, with oshmem enabled:
pinit_f.c:26:2: warning: #ident is a GCC extension
pshmem_init.c:31: warning: no previous prototype for 'pstart_pes'
pshmem_align.c:25: warning: no previous prototype for 'pshmemalign'
pshmem_align.c: In function 'pshmemalign':
pshmem_align.c:42: error: implicit decl
Fresh checkout did the trick. Sorry to bother.
Josh
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Joshua Ladd
Sent: Tuesday, February 25, 2014 6:51 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] Trunk is broken
SVN up. Reran autogen. I'm trying with a fresh checkou
SVN up. Reran autogen. I'm trying with a fresh checkout now.
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
Sent: Tuesday, February 25, 2014 6:48 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] Trunk is broken
Nope - that built fine too. I'm at a loss
ilto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
>> Sent: Tuesday, February 25, 2014 6:17 PM
>> To: Open MPI Developers
>> Subject: Re: [OMPI devel] Trunk is broken
>>
>> Odd - it is building fine for me on both Mac and Linux. Is this a git mirror
>>
efix-by-default
>
> From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
> Sent: Tuesday, February 25, 2014 6:17 PM
> To: Open MPI Developers
> Subject: Re: [OMPI devel] Trunk is broken
>
> Odd - it is building fine for me on both Mac and Linux. Is th
Developers
Subject: Re: [OMPI devel] Trunk is broken
Odd - it is building fine for me on both Mac and Linux. Is this a git mirror or
the actual svn checkout, or a tarball?
On Feb 25, 2014, at 3:11 PM, Joshua Ladd
mailto:josh...@mellanox.com>> wrote:
Ralph, maybe something didn't get
Odd - it is building fine for me on both Mac and Linux. Is this a git mirror or
the actual svn checkout, or a tarball?
On Feb 25, 2014, at 3:11 PM, Joshua Ladd wrote:
> Ralph, maybe something didn’t get pulled over in your OSC merge:
>
> Looks like a few routines were removed and were not re
Ralph, maybe something didn't get pulled over in your OSC merge:
Looks like a few routines were removed and were not replaced or were not
removed from other parts of the code where they are invoked
inompi/mpi/c/profile/paccumulate.c
The offending change set is: https://svn.open-mpi.org/trac/om
Temporary workaround: -mca btl ^vader
On Feb 8, 2014, at 10:11 AM, Ralph Castain wrote:
> Sorry to say, some recent commit has broken the trunk:
>
> rhc@bend002 examples]$ mpirun -n 3 ./hello_c
> [bend001:22289] *** Process received signal ***
> [bend001:22289] Signal: Segmentation fault (11)
Sorry to say, some recent commit has broken the trunk:
rhc@bend002 examples]$ mpirun -n 3 ./hello_c
[bend001:22289] *** Process received signal ***
[bend001:22289] Signal: Segmentation fault (11)
[bend001:22289] Signal code: Invalid permissions (2)
[bend001:22289] Failing at address: 0x7f354daaa00
ya, i'm fixing it now
On Oct 1, 2013, at 5:55 PM, Joshua Ladd wrote:
> Also getting a compile failure in the trunk:
>
> ./autogen.pl && ./configure
> --prefix=/hpc/home/USERS/joshual/ompi_trunk/really-the-trunk/ompi-install
> --with-mxm=/hpc/local/src/mxm2_release --with-fca=/opt/mellanox/f
Also getting a compile failure in the trunk:
./autogen.pl && ./configure
--prefix=/hpc/home/USERS/joshual/ompi_trunk/really-the-trunk/ompi-install
--with-mxm=/hpc/local/src/mxm2_release --with-fca=/opt/mellanox/fca --with-pmi
&& make -j 9 && make install
CC ess_slurm_module.lo
CCLD
FYI: this has been fixed and the temporary patch removed. Turned out to be a
problem with progress threads not getting completely cleaned up prior to exit,
resulting in multiple threads executing opal_finalize.
On Dec 24, 2012, at 10:43 AM, Ralph Castain wrote:
> FWIW: I have installed a temp
FWIW: I have installed a temporary patch that allows the trunk to run by no
longer finalizing OPAL. Once the param system has been repaired, this will be
removed. Meantime, at least you can run the trunk.
On Dec 24, 2012, at 10:39 AM, Ralph Castain wrote:
> Hi folks
>
> This is a heads-up to
Hi folks
This is a heads-up to all: It appears a recent commit has broken the trunk - I
think it relates to something done to the MCA parameter system. When running
across multiple nodes, the daemons segfault on finalize with a stacktrace of:
(gdb) where
#0 0x003dc4477e92 in _int_free () f
Turned out to be a faulty svn update. Getting a clean svn checkout
fixed the problem.
On Jun 1, 2009, at 10:04 AM, Rainer Keller wrote:
Hi Ralph,
of course, at first I was afraid this was afraid that these were
related to
pulling the OMPI_ALIGNMENT (and friends) configure to the OPAL lay
Hi Ralph,
of course, at first I was afraid this was afraid that these were related to
pulling the OMPI_ALIGNMENT (and friends) configure to the OPAL layer (r21330),
but failures I seen in MTT are related to windows (r21334).
Well AM_CONDITIONAL(WANT_PERUSE...) is in ./config/ompi_configure_optio
Hi folks
I'm getting the following build failures this morning - looks like something
crept in over the weekend?
ompi/peruse/Makefile.am:19: WANT_PERUSE does not appear in AM_CONDITIONAL
ompi/Makefile.am:155: `ompi/peruse/Makefile.am' included from here
ompi/Makefile.am: installing `config/depc
33 matches
Mail list logo
