On Jun 10, 2015, at 1:35 AM, Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> wrote: > >> I don't see any reason why this should be happening to you only >> sometimes; this code has been unchanged in *forever*. :-( > > It only happens since openmpi-v1.8.5-40-g7b9e672 which I tried to > build June 1th and on all versions following-up which I tried > (openmpi-v1.8.5-43-g0dd996b, openmpi-v1.8.5-44-g4ec7b80, and > openmpi-v1.8.5-46-g9f5f498) It didn't happen with openmpi-1.8.6rc1 > and before.
Very strange. Like I said, this particular part of the code has not changed in a very long time. Shrug. >> Regardless, I just pushed what should be a workaround to master >> and I'll PR it over to v1.8 and v1.10 (it'll take a day or so >> for these to show up in the nightly tarballs) -- it should avoid >> the issue altogether. > > Thank you very much for your help. I'll try to build the next > versions and let you know the results. Thanks. The nightly builds from last night should contain the workaround. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
