Yes - I fixed it in v1.8 immediately after the nightly tarball failed to build. 
So telling us it -was- broken is a stale report - a subsequent Jenkins run 
would show it as fixed.


> On Oct 23, 2014, at 6:07 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:
> 
> but fix was in the master
> jenkins complained about v1.8 where fix is not present.
> do I miss something?
> 
> On Thu, Oct 23, 2014 at 4:01 PM, Ralph Castain <r...@open-mpi.org 
> <mailto:r...@open-mpi.org>> wrote:
> My bad - I see what Gilles is talking about. Still need to figure out a way 
> to avoid these commit-by-commit complaints when later commits already fixed 
> the problem. Isn't there some way to educate Jenkins to avoid it?
> 
> 
>> On Oct 23, 2014, at 5:57 AM, Ralph Castain <r...@open-mpi.org 
>> <mailto:r...@open-mpi.org>> wrote:
>> 
>> I already fixed this immediately after it was detected. We don't want to 
>> backport the opal changes that occurred when we moved the BTLs down to OPAL. 
>> All that was required was to rename opal_process_info back to 
>> ompi_process_info
>> 
>> Mike: these stale Jenkins reports are causing people to waste time. Could 
>> you please first check to see if the problem was already fixed before 
>> sending bogus reports out?
>> 
>> Thanks
>> Ralph
>> 
>>> On Oct 23, 2014, at 2:29 AM, Gilles Gouaillardet 
>>> <gilles.gouaillar...@iferc.org <mailto:gilles.gouaillar...@iferc.org>> 
>>> wrote:
>>> 
>>> Mike,
>>> 
>>> the root cause is vader was not fully backported to v1.8
>>> (two OPAL_* macros were not backported to OMPI_*)
>>> 
>>> i fixed it in https://github.com/open-mpi/ompi-release/pull/49 
>>> <https://github.com/open-mpi/ompi-release/pull/49>
>>> 
>>> please note a similar warning is fixed in 
>>> https://github.com/open-mpi/ompi-release/pull/48 
>>> <https://github.com/open-mpi/ompi-release/pull/48>
>>> 
>>> Cheers,
>>> 
>>> Gilles
>>> 
>>> On 2014/10/23 17:14, Mike Dubman wrote:
>>>> *05:12:10* more information, such as the ld(1) and ld.so(8) manual pages.
>>>> 
>>>> *05:12:10*
>>>> ----------------------------------------------------------------------
>>>> 
>>>> *05:12:10* make[3]: Leaving directory
>>>> `/scrap/jenkins/workspace/hpc-ompi-shmem/label/r-vmb-centos5-u7-x86-64/ompi/mca/btl/vader'
>>>> 
>>>> *05:12:10* make[2]: Leaving directory
>>>> `/scrap/jenkins/workspace/hpc-ompi-shmem/label/r-vmb-centos5-u7-x86-64/ompi/mca/btl/vader'
>>>> 
>>>> *05:12:10* Making install in mca/btl/sm
>>>> 
>>>> *05:12:10* make[2]: Entering directory
>>>> `/scrap/jenkins/workspace/hpc-ompi-shmem/label/r-vmb-centos5-u7-x86-64/ompi/mca/btl/sm'
>>>> 
>>>> *05:12:10*   CC       mca_btl_sm_la-btl_sm.lo
>>>> 
>>>> *05:12:11*   CC       mca_btl_sm_la-btl_sm_component.lo
>>>> 
>>>> *05:12:12* btl_sm_component.c: In function 'mca_btl_sm_component_verify':
>>>> 
>>>> *05:12:12* btl_sm_component.c:161: error: 'mca_btl_sm_dummy_get' undeclared
>>>> (first use in this function)
>>>> 
>>>> *05:12:12* btl_sm_component.c:161: error: (Each undeclared identifier is
>>>> reported only once
>>>> 
>>>> *05:12:12* btl_sm_component.c:161: error: for each function it appears in.)
>>>> 
>>>> *05:12:12* btl_sm_component.c: In function 'mca_btl_sm_component_init':
>>>> 
>>>> *05:12:12* btl_sm_component.c:915: error: 'opal_process_info' undeclared
>>>> (first use in this function)
>>>> 
>>>> *05:12:12* make[2]: *** [mca_btl_sm_la-btl_sm_component.lo] Error 1
>>>> 
>>>> *05:12:12* make[2]: Leaving directory
>>>> `/scrap/jenkins/workspace/hpc-ompi-shmem/label/r-vmb-centos5-u7-x86-64/ompi/mca/btl/sm'
>>>> 
>>>> *05:12:12* make[1]: *** [install-recursive] Error 1
>>>> 
>>>> *05:12:12* make[1]: Leaving directory
>>>> `/scrap/jenkins/workspace/hpc-ompi-shmem/label/r-vmb-centos5-u7-x86-64/ompi'
>>>> 
>>>> *05:12:12* make: *** [install-recursive] Error 1
>>>> 
>>>> *05:12:12* Build step 'Execute shell' marked build as failure
>>>> 
>>>> *05:12:12* [BFA] Scanning build for known causes...
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> devel mailing list
>>>> de...@open-mpi.org <mailto:de...@open-mpi.org>
>>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel 
>>>> <http://www.open-mpi.org/mailman/listinfo.cgi/devel>
>>>> Link to this post: 
>>>> http://www.open-mpi.org/community/lists/devel/2014/10/16079.php 
>>>> <http://www.open-mpi.org/community/lists/devel/2014/10/16079.php>
>>> _______________________________________________
>>> devel mailing list
>>> de...@open-mpi.org <mailto:de...@open-mpi.org>
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel 
>>> <http://www.open-mpi.org/mailman/listinfo.cgi/devel>
>>> Link to this post: 
>>> http://www.open-mpi.org/community/lists/devel/2014/10/16081.php 
>>> <http://www.open-mpi.org/community/lists/devel/2014/10/16081.php>
> 
> 
> _______________________________________________
> devel mailing list
> de...@open-mpi.org <mailto:de...@open-mpi.org>
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel 
> <http://www.open-mpi.org/mailman/listinfo.cgi/devel>
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/16085.php 
> <http://www.open-mpi.org/community/lists/devel/2014/10/16085.php>
> 
> 
> 
> -- 
> 
> Kind Regards,
> 
> M.
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/16086.php

Reply via email to