This is fixed now. Jenkins update dropped this setting. We dealing with some other issue now. Will update later.
четверг, 21 июля 2016 г. пользователь Jeff Squyres (jsquyres) написал: > Gilles: Oh, sweet! This could answer a long-standing question: why PR's > sometimes fail with unexplained Libtool / depcomp problems. > > Artem: I'm mailing list several hours after your initial exchange with > Gilles, so you may have solved this by now, but since your Jenkins was > running multiple Open MPI builds simultaneously in the same workspace, that > could definitely lead to the Libtool / depcomp issues that we have talked > about previously (and potentially other issues). If you haven't done so > already, you will likely need to make sure that simultaneous OMPI Jenkins > builds are totally divorced from each other: different source dir, > different build dir, different install dir. > > > > > > On Jul 21, 2016, at 3:56 AM, Artem Polyakov <artpo...@gmail.com > <javascript:;>> wrote: > > > > Thank you for the input by the way. It sounds very useful! > > > > 2016-07-21 13:54 GMT+06:00 Artem Polyakov <artpo...@gmail.com > <javascript:;>>: > > Gilles, we are aware and working on this. > > > > 2016-07-21 13:53 GMT+06:00 Gilles Gouaillardet <gil...@rist.or.jp > <javascript:;>>: > > Folks, > > > > > > Mellanox Jenkins marks recent PR's as failed for very surprising reasons. > > > > > > mpirun --mca btl sm,self ... > > > > > > failed because processes could not contact each other. i was able to > reproduce this once on my workstation, > > > > and found the root cause was a dirty build and/or install dir. > > > > > > i added some debug in autogen.sh and found that : > > > > - the workspace (install dir) contains some old files > > > > - it seems all PR's use the same workspace (if it was clean, that would > be ok as long as Jenkins process only one PR at a time) > > > > - there are currently two PR's being processed for the ompi-release > repo, and per the log, they seem to use run from the very same directory > > > > - Jenkins for the pmix repo seems to suffer the same issue > > > > > > could someone have a look at this ? > > > > > > Cheers, > > > > > > Gilles > > > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org <javascript:;> > > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19247.php > > > > > > > > -- > > С Уважением, Поляков Артем Юрьевич > > Best regards, Artem Y. Polyakov > > > > > > > > -- > > С Уважением, Поляков Артем Юрьевич > > Best regards, Artem Y. Polyakov > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org <javascript:;> > > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19249.php > > > -- > Jeff Squyres > jsquy...@cisco.com <javascript:;> > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org <javascript:;> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19251.php -- ----- Best regards, Artem Polyakov (Mobile mail)
