Creating nightly hwloc snapshot git tarball was a success.
Snapshot: hwloc dev-1226-g64d92a8
Start time: Wed Aug 17 18:01:06 PDT 2016
End time: Wed Aug 17 18:04:45 PDT 2016
Your friendly daemon,
Cyrador
___
hwloc-devel mailing list
Creating nightly hwloc snapshot git tarball was a success.
Snapshot: hwloc dev-1230-g922cbec
Start time: Tue Aug 23 18:01:12 PDT 2016
End time: Tue Aug 23 18:04:47 PDT 2016
Your friendly daemon,
Cyrador
___
hwloc-devel mailing list
Just curious - will this ever be fixed? From today’s head of master:
In file included from info.c:46:0:
info.c: In function 'opal_info_dup_mode':
../../opal/util/info.h:112:31: warning: '%s' directive output may be truncated
writing up to 36 bytes into a region of size 27 [-Wformat-truncation=]
I suspect this is a stale message - I’m not seeing any problem with the website
> On Aug 29, 2018, at 12:55 PM, Howard Pritchard wrote:
>
> Hi Folks,
>
> Something seems to be borked up about the OMPI website. Got to website and
> you'll
> get some odd parsing error appearing.
>
> Howard
>
Still seeing this in today’s head of master:
info_subscriber.c: In function 'opal_infosubscribe_change_info':
../../opal/util/info.h:112:31: warning: '%s' directive output may be truncated
writing up to 36 bytes into a region of size 27 [-Wformat-truncation=]
#define OPAL_INFO_SAVE_PREFIX
Could you please send the output from “lstopo --of xml foo.xml” (the file
foo.xml) so I can try to replicate here?
> On Sep 4, 2018, at 12:35 PM, Shrader, David Lee wrote:
>
> Hello,
>
> I have run this issue by Howard, and he asked me to forward it on to the Open
> MPI devel mailing list.
-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 9.1.0 (clang-902.0.39.2)
> Target: x86_64-apple-darwin17.7.0
> Thread model: posix
> InstalledDir:
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>
>
>
>
>
>> On S
point it out!
Ralph
> On Oct 12, 2018, at 6:15 AM, Ralph H Castain wrote:
>
> Hi Stephan
>
>
>> On Oct 12, 2018, at 2:25 AM, Stephan Krempel > <mailto:krem...@par-tec.com>> wrote:
>>
>> Hallo Ralph,
>>
>>> I assume this (--with-
> On Oct 12, 2018, at 6:15 AM, Ralph H Castain wrote:
>
>> One point that remains open and is interesting for me is if I can
>> achieve the same with the 3.1.2 release of OpenMPI. Is it somehow
>> possible to configure it as there were the "--with-ompi-pmix-rt
Hello all
[I’m sharing this on the OMPI mailing lists (as well as the PMIx one) as PMIx
has become tightly integrated to the OMPI code since v2.0 was released]
The PMIx Community will once again be hosting a Birds-of-a-Feather meeting at
SuperComputing. This year, however, will be a little
> On Oct 17, 2018, at 3:32 AM, Stephan Krempel wrote:
>
>
> Hi Ralph.
>
One point that remains open and is interesting for me is if I can
achieve the same with the 3.1.2 release of OpenMPI. Is it somehow
possible to configure it as there were the "--with-ompi-pmix-rte"
;>> ORTE_SCHIZO_DETECTION=ORTE
>>> OMPI_COMMAND=./hello_env
>>> OMPI_MCA_orte_precondition_transports=f28d6577f6b6ac08-
>>> d92c0e73869e1cfa
>>> OMPI_MCA_orte_launch=1
>>> OMPI_APP_CTX_NUM_PROCS=1
>>> OMPI_MCA_pmix=^s1,s2,cray,isolated
>>> OMPI_MCA
Even PRRTE won’t allow you to stop the orted from initializing its PMIx server.
I’m not sure I really understand your objective. Remember, PMIx is just a
library - the orted opens it and uses it to interface to its client application
procs. It makes no sense to have some other process perform
Hi Stephan
Thanks for the clarification - that helps a great deal. You are correct that
OMPI’s orted daemons do more than just host the PMIx server library. However,
they are only active if you launch the OMPI processes using mpirun. This is
probably the source of the trouble you are seeing.
at I need to change? Do I have to set an MCA
> parameter to tell OpenMPI not to start orted, or does it need another
> hint in the client environment beside the stuff comming from the PMIx
> server helper library?
>
>
> Stephan
>
>
> On Tuesday, Oct 10 2018, 08:33
We already have the register_cleanup option in master - are you using an older
version of PMIx that doesn’t support it?
> On Oct 2, 2018, at 4:05 AM, Jeff Squyres (jsquyres) via devel
> wrote:
>
> FYI: https://github.com/open-mpi/ompi/issues/5798 brought up what may be the
> same issue.
>
Based on silence plus today’s telecon, the stale code has been removed:
https://github.com/open-mpi/ompi/pull/5827
> On Sep 26, 2018, at 7:00 AM, Ralph H Castain wrote:
>
> We are considering a “purge” of stale ORTE code and want to know if anyone is
> using it befor
Good lord - break away!!
> On Sep 28, 2018, at 11:11 AM, Barrett, Brian via devel
> wrote:
>
> All -
>
> In trying to clean up some warnings, I noticed one (around pack/unpack in
> net/if.h) that is due to a workaround of a bug in MacOS X 10.4.x and earlier.
> The simple way to remove the
I’m getting this error when trying to run a simple ring program on my Mac:
[Ralphs-iMac-2.local][[21423,14],0][btl_tcp_endpoint.c:742:mca_btl_tcp_endpoint_start_connect]
bind() failed: Invalid argument (22)
Anyone recognize the problem? It causes the job to immediately abort. This is
with
a rather add an .ompi_ignore and
> give an opportunity to power users do continue playing with it.
>
> George.
>
>
>> On Thu, Sep 20, 2018 at 8:04 PM Ralph H Castain wrote:
>> I already suggested the configure option, but it doesn’t solve the problem.
>> I wou
We have too many discussion threads overlapping on the same email chain - so
let’s break the discussion on the OFI problem into its own chain.
We have been investigating this locally and found there are a number of
conflicts between the MTLs and the OFI/BTL stepping on each other. The correct
ext major release to get this in.
>
>
> Arm
>
>
> On Thu, Sep 20, 2018, 7:18 PM Ralph H Castain <mailto:r...@open-mpi.org>> wrote:
> I suspect it is a question of what you tested and in which scenarios. Problem
> is that it can bite someone and there isn’t
MTL and able to use both
> of them interchangeably with no problem. I dont know what changed. libpsm2?
>
>
> Arm
>
>
> On Thu, Sep 20, 2018, 7:06 PM Ralph H Castain <mailto:r...@open-mpi.org>> wrote:
> We have too many discussion threads overlappin
We are considering a “purge” of stale ORTE code and want to know if anyone is
using it before proceeding. With the advent of PMIx, several ORTE features are
no longer required by OMPI itself. However, we acknowledge that it is possible
that someone out there (e.g., a researcher) is using them.
FYI: I have deleted all the old OMPI tags from PRRTE, so we have a clean repo
to work with now.
> On Dec 17, 2018, at 5:58 PM, Ralph H Castain wrote:
>
> Hello all
>
> For those of you working with ORTE and/or PRRTE, GitHub has severed the
> parent/child relationshi
Hello all
For those of you working with ORTE and/or PRRTE, GitHub has severed the
parent/child relationship between the OMPI and PRRTE repositories. Thus, we
will no longer be able to directly “pull” changes made to ORTE downstream into
PRRTE.
This marks the end of direct support for ORTE
The PMIx community, representing a consortium of research, academic, and
industry partners, is pleased to announce the release of the PMIx v3.0 Standard
document. The document can be obtained from:
* the PMIx website at
https://pmix.org/wp-content/uploads/2018/12/pmix-standard-3.0.pdf
* the
The security scanner has apologized for a false positive and fixed their system
- the site has been restored.
Ralph
> On Dec 22, 2018, at 12:12 PM, Ralph H Castain wrote:
>
> Hello all
>
> Apologies to everyone, but I received an alert this moring that malware has
Hello all
Apologies to everyone, but I received an alert this moring that malware has
been detected on the www.open-mpi.org site. I have tried to contact the hosting
agency and the security scanners, but nobody is around on this pre-holiday
weekend.
Accordingly, I have taken the site OFFLINE
The PMIx community, representing a consortium of research, academic, and
industry partners, is pleased to announce the release of the PMIx v2.1 Standard
document. The document can be obtained from:
* the PMIx website at
https://pmix.org/wp-content/uploads/2018/12/pmix-standard-2.1.pdf
Hi folks
Given a growing use of PRRTE plus OMPI’s announced plans to phase out ORTE in
favor of PRRTE, it seems the time has come to begin generating formal releases
of PRRTE. Accordingly, I have created a v3.0.0 release candidate for folks to
(hopefully) test:
Hi folks
Per today’s telecon, I have moved the Perl MTT client into its own repository:
https://github.com/open-mpi/mtt-legacy. All the Python client code has been
removed from that repo.
The original MTT repo remains at https://github.com/open-mpi/mtt. I have a PR
to remove all the Perl
gt;
>
>> On Sep 14, 2018, at 11:23 AM, Ralph H Castain wrote:
>>
>> Afraid I’m not familiar with that script - what does it do?
>>
>>
>>> On Sep 14, 2018, at 7:46 AM, Christoph Niethammer
>>> wrote:
>>>
>>> Works for
acement?
>
> Best
> Christoph Niethammer
>
> - Mensaje original -
> De: "Open MPI Developers"
> Para: "Open MPI Developers"
> CC: "Jeff Squyres"
> Enviados: Martes, 11 de Septiembre 2018 20:37:40
> Asunto: Re: [OMPI devel]
Are we good to go with this changeover? If so, I’ll delete the Perl client from
the main MTT repo.
> On Sep 14, 2018, at 10:06 AM, Jeff Squyres (jsquyres) via devel
> wrote:
>
> On Sep 14, 2018, at 12:37 PM, Gilles Gouaillardet
> wrote:
>>
>> IIRC mtt-relay is not only a proxy (squid can
at it when binding. I’ll
try to poke at it a bit.
> On Sep 11, 2018, at 9:17 AM, Shrader, David Lee wrote:
>
> Here's the xml output from lstopo. Thank you for taking a look!
> David
>
> From: devel on behalf of Ralph H Castain
>
> Sent: Monday, September 10, 2018 5:1
Done!
> On Feb 26, 2019, at 8:33 AM, Brice Goglin wrote:
>
> Hello Jeff
>
> Looks like I am not allowed to modify the page but I'll be at the meeting ;)
>
> Brice
>
>
>
> Le 26/02/2019 à 17:13, Jeff Squyres (jsquyres) via devel a écrit :
>> Gentle reminder to please sign up for the
(see scripts/deploy.sh) seems to be invalid. This
> is run on the Travis CI build so I don’t know how to check that. Can you help?
> deb
>
>
> From: mtt-devel on behalf of Ralph H
> Castain
> Reply-To: Development list for the MPI Testing Tool
>
> Date: Thursday, Februa
I apologize - I haven’t been closely following this. Did you do some kind of
“git rm -rf” on the contents of gh-pages? I don’t see anything in the commit
history for that branch other than a last auto-update 2 days ago.
> On Feb 28, 2019, at 7:34 AM, Rezanka, Deb via mtt-devel
> wrote:
>
>
I would recommend just removing it - frankly, I’m surprised it is in there as
the code was deemed non-production-ready.
> On Feb 14, 2019, at 5:11 PM, Gilles Gouaillardet wrote:
>
> Folks,
>
>
> The rml/ofi component has been removed from master.
>
> Then common/ofi was later removed from
There is a coll/sync component that will automatically inject those barriers
for you so you don’t have to add them to your code. Controlled by MCA param:
coll_sync_barrier_before: Do a synchronization before each Nth collective
coll_sync_barrier_after: Do a synchronization after each Nth
Not exactly. The problem is that rank=0 initially falls behind because it is
doing more work - i.e., it has to receive all the buffers and do something with
them. As a result, it doesn’t get to post the next allreduce before the
messages from the other participants arrive - which means that
201 - 242 of 242 matches
Mail list logo
