[OMPI devel] XRC_INI QPs and modify_qp
To me, it looks like Open MPI in xoob_send_qp_connect() attempts to set the max_dest_rd_atomic attribute in the transition from INIT to RTR, even for XRC_INI QPs. This is illegal, according to the ib_modify_qp_is_ok() function in ib_core. In particular, IBV_QP_MAX_DEST_RD_ATOMIC is not part of either the required nor optional set of attributes for this transition for XRC_INI QPs. Thxs, Håkon
Re: [OMPI devel] XRC_INI QPs and modify_qp
I filed https://github.com/open-mpi/ompi/issues/1839 to track this issue. Thanks! > On Jul 1, 2016, at 6:57 AM, Håkon Bugge wrote: > > To me, it looks like Open MPI in xoob_send_qp_connect() attempts to set the > max_dest_rd_atomic attribute in the transition from INIT to RTR, even for > XRC_INI QPs. This is illegal, according to the ib_modify_qp_is_ok() function > in ib_core. In particular, IBV_QP_MAX_DEST_RD_ATOMIC is not part of either > the required nor optional set of attributes for this transition for XRC_INI > QPs. > > > > Thxs, Håkon > > > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Searchable archives: > http://www.open-mpi.org/community/lists/devel/2016/07/19144.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
[OMPI devel] Additional bot:retest target for IBM Jenkins: bot:ibm:retest
I added a feature to IBM's Jenkins setup yesterday that other orgs doing Jenkins CI testing might find helpful to add as well. We have the retest target for all of the Jenkins systems to re-test a particular PR: *bot:retest* I wanted an additional target that would trigger only the IBM Jenkins to re-test. This is helpful if we have a local issue with our Jenkins setup and don't want to force all of the Jenkins CI tests to fire at other organizations. So as of today you can specify the following to just get the IBM CI tests to re-test: *bot:ibm:retest* It might take a few minutes to kick off the build since we use a polling model (~2-5 minutes), but it will kick off only the IBM Jenkins CI tests. You can still use the "bot:retest" target to trigger all of the Jenkins services including IBM to re-test. I hope folks find this useful when working on PRs. -- Josh For those organizations interested in how to set this up here are the instructions - just adjusting the regular expression used in the build trigger: 1) Enter the 'configuration' in the Jenkins project you have setup to track GitHub PRs 2) Under "Build Triggers" -> "GitHub Pull Request Builder" - Click on "Advanced..." - Set "Trigger phrase" to .*bot:(ibm:)?retest.* Set the 'ibm' to your organization's short name, whatever you want it to be. Then let the list know.
Re: [OMPI devel] Additional bot:retest target for IBM Jenkins: bot:ibm:retest
Josh: many thanks, this will be super useful. Do we have a wiki page on setting up your own CI? Adding this kind of regexp to your Jenkins would seem like some knowledge that we should capture for others to use. > On Jul 1, 2016, at 9:37 AM, Josh Hursey wrote: > > I added a feature to IBM's Jenkins setup yesterday that other orgs doing > Jenkins CI testing might find helpful to add as well. > > We have the retest target for all of the Jenkins systems to re-test a > particular PR: > bot:retest > > I wanted an additional target that would trigger only the IBM Jenkins to > re-test. This is helpful if we have a local issue with our Jenkins setup and > don't want to force all of the Jenkins CI tests to fire at other > organizations. > > So as of today you can specify the following to just get the IBM CI tests to > re-test: > bot:ibm:retest > > It might take a few minutes to kick off the build since we use a polling > model (~2-5 minutes), but it will kick off only the IBM Jenkins CI tests. You > can still use the "bot:retest" target to trigger all of the Jenkins services > including IBM to re-test. > > I hope folks find this useful when working on PRs. > > -- Josh > > > For those organizations interested in how to set this up here are the > instructions - just adjusting the regular expression used in the build > trigger: > > 1) Enter the 'configuration' in the Jenkins project you have setup to track > GitHub PRs > 2) Under "Build Triggers" -> "GitHub Pull Request Builder" > - Click on "Advanced..." > - Set "Trigger phrase" to > .*bot:(ibm:)?retest.* > > Set the 'ibm' to your organization's short name, whatever you want it to be. > Then let the list know. > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19146.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] Additional bot:retest target for IBM Jenkins: bot:ibm:retest
I added a user note here: https://github.com/open-mpi/ompi/wiki/PRJenkins#how-to-re-trigger-jenkins-testing I added a developer setup note here: https://github.com/open-mpi/ompi/wiki/PRJenkinsSetupFirewall#setting-up-the-internaljenkins-job The above developer link is for the more complex setup, I don't think we have a page for the more simple setup. On Fri, Jul 1, 2016 at 8:47 AM, Jeff Squyres (jsquyres) wrote: > Josh: many thanks, this will be super useful. > > Do we have a wiki page on setting up your own CI? Adding this kind of > regexp to your Jenkins would seem like some knowledge that we should > capture for others to use. > > > > > On Jul 1, 2016, at 9:37 AM, Josh Hursey wrote: > > > > I added a feature to IBM's Jenkins setup yesterday that other orgs doing > Jenkins CI testing might find helpful to add as well. > > > > We have the retest target for all of the Jenkins systems to re-test a > particular PR: > > bot:retest > > > > I wanted an additional target that would trigger only the IBM Jenkins to > re-test. This is helpful if we have a local issue with our Jenkins setup > and don't want to force all of the Jenkins CI tests to fire at other > organizations. > > > > So as of today you can specify the following to just get the IBM CI > tests to re-test: > > bot:ibm:retest > > > > It might take a few minutes to kick off the build since we use a polling > model (~2-5 minutes), but it will kick off only the IBM Jenkins CI tests. > You can still use the "bot:retest" target to trigger all of the Jenkins > services including IBM to re-test. > > > > I hope folks find this useful when working on PRs. > > > > -- Josh > > > > > > For those organizations interested in how to set this up here are the > instructions - just adjusting the regular expression used in the build > trigger: > > > > 1) Enter the 'configuration' in the Jenkins project you have setup to > track GitHub PRs > > 2) Under "Build Triggers" -> "GitHub Pull Request Builder" > > - Click on "Advanced..." > > - Set "Trigger phrase" to > > .*bot:(ibm:)?retest.* > > > > Set the 'ibm' to your organization's short name, whatever you want it to > be. Then let the list know. > > ___ > > devel mailing list > > de...@open-mpi.org > > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19146.php > > > -- > 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 > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19147.php >
Re: [OMPI devel] Additional bot:retest target for IBM Jenkins: bot:ibm:retest
Sweet; thanks Josh. > On Jul 1, 2016, at 10:50 AM, Josh Hursey wrote: > > I added a user note here: > > https://github.com/open-mpi/ompi/wiki/PRJenkins#how-to-re-trigger-jenkins-testing > > I added a developer setup note here: > > https://github.com/open-mpi/ompi/wiki/PRJenkinsSetupFirewall#setting-up-the-internaljenkins-job > > The above developer link is for the more complex setup, I don't think we have > a page for the more simple setup. > > > On Fri, Jul 1, 2016 at 8:47 AM, Jeff Squyres (jsquyres) > wrote: > Josh: many thanks, this will be super useful. > > Do we have a wiki page on setting up your own CI? Adding this kind of regexp > to your Jenkins would seem like some knowledge that we should capture for > others to use. > > > > > On Jul 1, 2016, at 9:37 AM, Josh Hursey wrote: > > > > I added a feature to IBM's Jenkins setup yesterday that other orgs doing > > Jenkins CI testing might find helpful to add as well. > > > > We have the retest target for all of the Jenkins systems to re-test a > > particular PR: > > bot:retest > > > > I wanted an additional target that would trigger only the IBM Jenkins to > > re-test. This is helpful if we have a local issue with our Jenkins setup > > and don't want to force all of the Jenkins CI tests to fire at other > > organizations. > > > > So as of today you can specify the following to just get the IBM CI tests > > to re-test: > > bot:ibm:retest > > > > It might take a few minutes to kick off the build since we use a polling > > model (~2-5 minutes), but it will kick off only the IBM Jenkins CI tests. > > You can still use the "bot:retest" target to trigger all of the Jenkins > > services including IBM to re-test. > > > > I hope folks find this useful when working on PRs. > > > > -- Josh > > > > > > For those organizations interested in how to set this up here are the > > instructions - just adjusting the regular expression used in the build > > trigger: > > > > 1) Enter the 'configuration' in the Jenkins project you have setup to track > > GitHub PRs > > 2) Under "Build Triggers" -> "GitHub Pull Request Builder" > > - Click on "Advanced..." > > - Set "Trigger phrase" to > > .*bot:(ibm:)?retest.* > > > > Set the 'ibm' to your organization's short name, whatever you want it to > > be. Then let the list know. > > ___ > > devel mailing list > > de...@open-mpi.org > > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: > > http://www.open-mpi.org/community/lists/devel/2016/07/19146.php > > > -- > 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 > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19147.php > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19148.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
