Ralph,
I can do that starting from monday
Cheers,
Gilles
Ralph Castain wrote:
>Thanks Brice!
>
>Our 1.8 branch probably has another 2 or so years in it, but I think we can
>lock it down fairly soon. Since we’ve shaken a lot of the bugs out of 1.8, we
>are now seeing the “adoption wave” that
Thanks Brice!
Our 1.8 branch probably has another 2 or so years in it, but I think we can
lock it down fairly soon. Since we’ve shaken a lot of the bugs out of 1.8, we
are now seeing the “adoption wave” that is causing bug reports. Once we get
thru this, I expect things will settle down again.
Le 12/12/2014 07:36, Gilles Gouaillardet a écrit :
> Brice,
>
> ompi master is based on hwloc 1.9.1, isn't it ?
Yes sorry, I am often confused by all these OMPI vs hwloc branch numbers.
>
> if some backport is required for hwloc 1.7.2 (used by ompi v1.8), then
> could you please update the hwloc
Brice,
ompi master is based on hwloc 1.9.1, isn't it ?
if some backport is required for hwloc 1.7.2 (used by ompi v1.8), then
could you please update the hwloc v1.7 branch ?
Cheers,
Gilles
On 2014/12/12 15:16, Brice Goglin wrote:
> Yes.
>
> In theory, everything that's in hwloc/v1.8 should go
Yes.
In theory, everything that's in hwloc/v1.8 should go to OMPI/master.
And most of it should go to v1.8 too, but that may require some
backporting rework. I can update hwloc/v1.7 if that helps.
Brice
Le 12/12/2014 03:10, Gilles Gouaillardet a écrit :
> Brice,
>
> should this fix be backpor
Brice,
should this fix be backported to both master and v1.8 ?
Cheers,
Gilles
On 2014/12/12 7:46, Brice Goglin wrote:
> This problem was fixed in hwloc upstream recently.
>
> https://github.com/open-mpi/hwloc/commit/790aa2e1e62be6b4f37622959de9ce3766ebc57e
> Brice
>
>
> Le 11/12/2014 23:40,
