If we are serious about this problem I don't see why we can't create a repo
for this data and keep the history of all measurements.
Is there any chance that we will not came up with well defined set of tests
and drop the ball here?
пятница, 26 августа 2016 г. пользователь George Bosilca написал:
Arm repo is a good location until we converge to a well-defined set of
tests.
George.
On Thu, Aug 25, 2016 at 1:44 PM, Artem Polyakov wrote:
> That's a good question. I have results myself and I don't know where to
> place them.
> I think that Arm's repo is not a right place to collect the d
That's a good question. I have results myself and I don't know where to
place them.
I think that Arm's repo is not a right place to collect the data.
Jeff, can we create the repo in open mpi organization on github or do we
have something appropriate already?
четверг, 25 августа 2016 г. пользовате
The following organizations have still not filled out the spreadsheet:
* Mellanox
* AMD
* ORNL
* Dresden
* NVIDIA
Please fill it out by COB tomorrow, Fri, Aug 25, 2016.
Thanks.
> On Aug 17, 2016, at 8:33 PM, Jeff Squyres (jsquyres)
> wrote:
>
> It's that time of year again!
>
> It's that t
__malloc_initialize_hook got “poisoned” in a newer release of glibc. We
disabled use of that symbol in 2.0.x. It might be worth adding to 1.10.4 as
well.
-Nathan
> On Aug 25, 2016, at 8:09 AM, Karol Mroz wrote:
>
> __malloc_initialize_hook
___
deve
Good morning Gilles and Franz-Joseph.
Gilles,
You're absolutely right...compilation is not actually at fault. The report
I received stated that the removal of __malloc_initialize_hook from
glibc2.24 was causing a build failure. Apparently I took the report too
literally, and in order to rush a fi
Thanks Paul -- fixed for the v2.0.1 release in
https://github.com/open-mpi/ompi-release/pull/1342.
> On Aug 25, 2016, at 1:49 AM, Paul Hargrove wrote:
>
> A run of "spell README" produces (after manual filtering) the following
> misspelled words:
> appliation
> applicaions
> availble
> compat
Hi Artem,
Thanks for the links. I tested now with 1.10.3, 2.0.0+sm/vader performance
regression patch under
https://github.com/hjelmn/ompi/commit/4079eec9749e47dddc6acc9c0847b3091601919f.patch
and master. I will do the 2.0.1rc in the next days as well.
Is it possible to add me to the results rep
I just noticed: the new mailman instance we have at NMC is successfully
handling DMARC issues. Yay!
>From the "If You Care" department...
If you recall, we had a mass-unsubscription event a few months ago when someone
from @yahoo.fr posted to the users mailing list. That mail was dutifully se
Correct.
There is a single "v2.x" branch that was branched from master a while ago (I
didn't check, but I assume the hash Gilles cites below is correct). v2.0.0 is
tagged on that branch.
Git branches and v2.0.x and v2.x plans were a topic we discussed in the
face-to-face meeting in Dallas las
Travis had a fairly significant event starting around 2pm US Eastern yesterday
that has resulted in a fairly large backlog. Apparently the issue has been
resolved and they are now working through the backlog:
https://www.traviscistatus.com/incidents/4mvp857qx8bw
Pending PRs should eventual
Hi Ralph,
Thanks for that, I'll test it out tomorrow. If it doesn't make it in 2.0.1,
that's fine - I'll just apply the patch myself.
Cheers,
Ben
-Original Message-
From: devel [mailto:devel-boun...@lists.open-mpi.org] On Behalf Of
r...@open-mpi.org
Sent: Thursday, 25 August 2016 2:12
12 matches
Mail list logo
