Re: [OMPI devel] 1.5.2rc1 is borked
1.5.2rc2 is now posted in the usual location. Please give it a spin! (note that the original subject line of this mail was incorrect -- it should have been "1.5.***2**rc1 is borked") On Feb 14, 2011, at 11:01 PM, Jeff Squyres wrote: > Sorry folks -- the release-building script caught the error, but it didn't > *print* the error, so George/I thought it had completed successfully. The > nightly build script, however, *did* print the error -- and I just confirmed > that 1.5.1rc1 is borked. > > We'll fix it tomorrow. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] v1.5 branch on mercurial mirror is hosed
No, it's not any problem you caused. The official HG mirror is listed here: http://www.open-mpi.org/svn/mercurial.php This mirror is maintained solely at Indiana U (the hosting provider for all of OMPI's internet services). Every 15 minutes, it examines SVN for new commits and adds them to the hg repo using the following command: hg convert https://svn.open-mpi.org/svn/ompi $outpath/ompi-svn-mirror Specifically, it's a built-in mercurial command to dump from SVN to a mercurial repo. Specifically, this is a one-way, read-only dump from SVN to the repo. It nicely to preserves all SVN branches and tags in the output hg repo. But it looks like something bad happened over time. There are currently *three* heads that have the "v1.5" label, but there's only one "v1.5" branch. I'm not quite sure how this happened -- the v1.5 branch should have been created once and then had all v1.5 changes applied to it automatically (i.e., follow the changes on the SVN v1.5 branch). Still investigating... On Feb 15, 2011, at 11:41 AM, Nikolay Piskun wrote: > This maybe to the change that I send to both OMPI and Bull. Could you please > send me the details. > > > Nikolay Piskun | Director of Continuing Engineering | Totalview Technologies | > Rogue Wave Software Inc | 24 Prime Parkway, Natick, MA 01760 | p > 508-652-7739| > nikolay.pis...@roguewave.com > www.roguewave.com > > >> -Original Message- >> From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On >> Behalf Of Jeff Squyres >> Sent: Tuesday, February 15, 2011 11:31 AM >> To: Open Developers >> Subject: [OMPI devel] v1.5 branch on mercurial mirror is hosed >> >> Bull has noticed that the v1.5 branch on the official OMPI hg mirror >> somehow got hosed (ping me if you want/care about the details). The >> other branches look like they're ok. >> >> We're investigating. >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> >> ___ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] v1.5 branch on mercurial mirror is hosed
This maybe to the change that I send to both OMPI and Bull. Could you please send me the details. Nikolay Piskun | Director of Continuing Engineering | Totalview Technologies | Rogue Wave Software Inc | 24 Prime Parkway, Natick, MA 01760 | p 508-652-7739| nikolay.pis...@roguewave.com www.roguewave.com > -Original Message- > From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On > Behalf Of Jeff Squyres > Sent: Tuesday, February 15, 2011 11:31 AM > To: Open Developers > Subject: [OMPI devel] v1.5 branch on mercurial mirror is hosed > > Bull has noticed that the v1.5 branch on the official OMPI hg mirror > somehow got hosed (ping me if you want/care about the details). The > other branches look like they're ok. > > We're investigating. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
[OMPI devel] v1.5 branch on mercurial mirror is hosed
Bull has noticed that the v1.5 branch on the official OMPI hg mirror somehow got hosed (ping me if you want/care about the details). The other branches look like they're ok. We're investigating. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] --enable-opal-multi-threads
On Feb 15, 2011, at 9:24 AM, Eugene Loh wrote: > Ralph Castain wrote: > >> On Feb 14, 2011, at 9:26 PM, Abhishek Kulkarni wrote: >> >>> On Mon, 14 Feb 2011, Ralph Castain wrote: >>> If the ability to turn "on" thread support is missing from 1.5, then that is an error. >>> No, it was changed from "--enable-mpi-threads" to >>> "--enable-opal-multi-threads" on the trunk in r22841 [1]. >>> >>> If the changeset has not been brought over to v1.5, it indeed looks like an >>> anachronism in the README. >>> >>> [1] https://svn.open-mpi.org/trac/ompi/changeset/22841 >>> >> My point is that it isn't an anachronism in the README, but an error in 1.5 >> - it needs to have the ability to turn on thread safety. >> > I'm not sure if we're making progress here. So far as I can tell, the v1.5 > README talks about --enable-opal-multi-threads. This option does not > otherwise appear in v1.5, but only in the trunk. So, to make the v1.5 README > consistent with the v1.5 source code (as opposed to talking about features > that will appear in unspecified future releases), either: > > *) the comment should be removed from the README, or > > *) opal-multi-threads should be CMRed to v1.5 My point is that option 2 needs to be done - not sure how much clearer I can be :-) > On Feb 14, 2011, at 5:36 PM, Eugene Loh wrote: > In the v1.5 README, I see this: > > --enable-opal-multi-threads > Enables thread lock support in the OPAL and ORTE layers. Does > not enable MPI_THREAD_MULTIPLE - see above option for that feature. > This is currently disabled by default. > > I don't otherwise find opal-multi-threads at all in this branch. It > seems to me, for such an option, one needs to move to the trunk. > > Is this an error (anachronism) in the v1.5 README? > > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] --enable-opal-multi-threads
Ralph Castain wrote: On Feb 14, 2011, at 9:26 PM, Abhishek Kulkarni wrote: On Mon, 14 Feb 2011, Ralph Castain wrote: If the ability to turn "on" thread support is missing from 1.5, then that is an error. No, it was changed from "--enable-mpi-threads" to "--enable-opal-multi-threads" on the trunk in r22841 [1]. If the changeset has not been brought over to v1.5, it indeed looks like an anachronism in the README. [1] https://svn.open-mpi.org/trac/ompi/changeset/22841 My point is that it isn't an anachronism in the README, but an error in 1.5 - it needs to have the ability to turn on thread safety. I'm not sure if we're making progress here. So far as I can tell, the v1.5 README talks about --enable-opal-multi-threads. This option does not otherwise appear in v1.5, but only in the trunk. So, to make the v1.5 README consistent with the v1.5 source code (as opposed to talking about features that will appear in unspecified future releases), either: *) the comment should be removed from the README, or *) opal-multi-threads should be CMRed to v1.5 On Feb 14, 2011, at 5:36 PM, Eugene Loh wrote: In the v1.5 README, I see this: --enable-opal-multi-threads Enables thread lock support in the OPAL and ORTE layers. Does not enable MPI_THREAD_MULTIPLE - see above option for that feature. This is currently disabled by default. I don't otherwise find opal-multi-threads at all in this branch. It seems to me, for such an option, one needs to move to the trunk. Is this an error (anachronism) in the v1.5 README?
Re: [OMPI devel] --enable-opal-multi-threads
On Feb 14, 2011, at 9:26 PM, Abhishek Kulkarni wrote: > > > On Mon, 14 Feb 2011, Ralph Castain wrote: > >> If the ability to turn "on" thread support is missing from 1.5, then that is >> an error. >> > > No, it was changed from "--enable-mpi-threads" to > "--enable-opal-multi-threads" on the trunk in r22841 [1]. I know - I did it :-) > > If the changeset has not been brought over to v1.5, it indeed looks like an > anachronism in the README. > > [1] https://svn.open-mpi.org/trac/ompi/changeset/22841 My point is that it isn't an anachronism in the README, but an error in 1.5 - it needs to have the ability to turn on thread safety. > >> >> On Feb 14, 2011, at 5:36 PM, Eugene Loh wrote: >> >>> In the v1.5 README, I see this: >>> >>> --enable-opal-multi-threads >>> Enables thread lock support in the OPAL and ORTE layers. Does >>> not enable MPI_THREAD_MULTIPLE - see above option for that feature. >>> This is currently disabled by default. >>> >>> I don't otherwise find opal-multi-threads at all in this branch. It seems >>> to me, for such an option, one needs to move to the trunk. >>> >>> Is this an error (anachronism) in the v1.5 README? >>> ___ >>> devel mailing list >>> de...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> >> >> ___ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
