I beg to differ on the Cisco case - some of those errors come directly from the 
Cisco MTT.


> On Apr 25, 2016, at 6:50 AM, Gilles Gouaillardet 
> <gilles.gouaillar...@gmail.com> wrote:
> 
> Cisco mtt looks clean
> since ompi_tests repo is private, it cannot be automatically pulled unless a 
> password is saved (https) or a public key was uploaded to github (ssh)
> for that reason, I would not simply assume the latest test suite is used :-(
> and fwiw, Jeff uses an internally mirrored repo for ompi-tests, so it Cisco 
> clusters should use the latest test suites.
> 
> Geoffrey,
> can you please comment on the config of the ibm cluster ?
> 
> Cheers,
> 
> Gilles
> 
> On Monday, April 25, 2016, Ralph Castain <r...@open-mpi.org 
> <javascript:_e(%7B%7D,'cvml','r...@open-mpi.org');>> wrote:
> I don’t know - this isn’t on my machine, but rather in the weekend and 
> nightly MTT reports. I’m assuming folks are running the latest test suite, 
> but...
> 
> 
>> On Apr 25, 2016, at 6:20 AM, Gilles Gouaillardet 
>> <gilles.gouaillar...@gmail.com <>> wrote:
>> 
>> Ralph,
>> 
>> can you make sure the ibm test suite is up to date ?
>> I pushed a fix for datatypes a few days ago, and it should be fine now.
>> 
>> I will double check this tomorrow anyway
>> 
>> Cheers,
>> 
>> Gilles
>> 
>> On Monday, April 25, 2016, Ralph Castain <r...@open-mpi.org <>> wrote:
>> I’m seeing some consistent errors in the 1.10.3rc MTT results and would 
>> appreciate it if folks could check them out:
>> 
>> ONESIDED:
>> onesided/cxx_win_attr:
>> [**ERROR**]: MPI_COMM_WORLD rank 0, file cxx_win_attr.cc:50:
>> Win::Get_attr: Got wrong value for disp unit
>> [**ERROR**]: MPI_COMM_WORLD rank 1, file cxx_win_attr.cc:50:
>> Win::Get_attr: Got wrong value for disp
>> 
>> 
>> DATATYPE:
>> datatype/predefined-datatype-name
>> MPI_LONG_LONG                    != MPI_LONG_LONG_INT
>> 
>> 
>> LOOP SPAWN:
>> too many retries sending message to <addr>, giving up
>> 
>> Thanks
>> Ralph
>> 
>> _______________________________________________
>> devel mailing list
>> 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/2016/04/18809.php 
>> <http://www.open-mpi.org/community/lists/devel/2016/04/18809.php>_______________________________________________
>> devel mailing list
>> 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/2016/04/18810.php 
>> <http://www.open-mpi.org/community/lists/devel/2016/04/18810.php>
> _______________________________________________
> 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/2016/04/18812.php

Reply via email to