ftb', 'HASH(0x19ebba0)',
'HASH(0x19e4940)', 'HASH(0x19df600)') called at
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Test/Run.pm line 552
MTT::Test::Run::_do_run('Config::IniFiles=HASH(0x19dfea0)', 'test run:
ftb', 'HASH(0x19ebba0)', 'HASH(0x19dfdf0)', 'HASH(0x19e4940)',
'/u/ftbteam/ft
On Nov 9, 2010, at 1:00 AM, DongInn Kim wrote:
> No, I did not know that it should be added in the MPI Get phase.
You have to call all the phases, even if they don't "do" anything. That's why
we have no-op / alreadyinstalled versions of plugins, for example. Each phase
sets up data
Hi list,
Can someone give me an exhaustive list of the options that can be used
for any single binary when calling mpirun for the mpmd model, vs those
that are global to the job? I couldn't find it anywhere.
For example, --hostfile can be specified for each binary in the job,
while it looks like
In digging through some configury to sort out some recent bugs, I found some
more M4 macros and shell variables that are OMPI_ when they really should
be OPAL_ (specifically: all the macros in opal/contrib/opal_functions.m4).
I used the contrib/search_replace.pl script to ferret out all such
Jeff Squyres, le Mon 08 Nov 2010 15:18:01 +0100, a écrit :
> Here's a Trac colorized diff between the 1.0 branch from r2349 and the
> current HEAD:
>
> https://svn.open-mpi.org/trac/hwloc/changeset?old_path=/branches/v1.0=2349_path=/branches/v1.0=HEAD):
>
> The only interface change I see is
Jeff Squyres, le Mon 08 Nov 2010 15:38:31 +0100, a écrit :
> The last one is what I'm not sure about, but what I'm inferring from Samuel's
> statement about "API breaks".
Actually you can have an API break without an ABI break. Here, old
applications should work fine. They'll just not be able
Brice Goglin, le Mon 08 Nov 2010 16:57:44 +0100, a écrit :
> Le 08/11/2010 15:38, Jeff Squyres a écrit :
> > Short version:
> > --
> >
> > I have not looked closely -- I *think* APIs have been added and changed
> > since v1.0. As such, I *think* the libtool .so version number for 1.1
On Nov 9, 2010, at 12:49 PM, Samuel Thibault wrote:
>> But the object structure has been extended, cache attributes were
>> extended,
>
> Extension is not a problem, provided that offsets are still the same
> (i.e. the old C structure appears first in the new C structure)
>
>> machine
Le 09/11/2010 18:49, Samuel Thibault a écrit :
> That is not a problem here. The attr field of hwloc_obj will be NULL,
> that's all, the application won't ever read it anyway.
>
We will see segfaults if applications were looking at machine->attr
without checking that it's non-NULL. It's a
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.1rc2r2759
Start time: Tue Nov 9 21:01:05 EST 2010
End time: Tue Nov 9 21:03:21 EST 2010
Your friendly daemon,
Cyrador
10 matches
Mail list logo
