Re: [OMPI devel] Failures

2015-01-19 Thread Gilles Gouaillardet
George, i was able to reproduce the hang with intel compiler 14.0.0 but i am still unable to reproduce it with intel compiler 14.3 i was not able to understand where the issue come from, so i could not create an appropriate test in configure at this stage, i can only recommend you update your co

Re: [OMPI devel] Failures

2015-01-16 Thread George Bosilca
Your patch solve the issue with opal_tree. The opal_lifo remains broken. George. On Fri, Jan 16, 2015 at 5:12 AM, Gilles Gouaillardet < gilles.gouaillar...@iferc.org> wrote: > George, > > i pushed > https://github.com/open-mpi/ompi/commit/ac16970d21d21f529f1ec01ebe0520843227475b > in order t

Re: [OMPI devel] Failures

2015-01-16 Thread Gilles Gouaillardet
George, i pushed https://github.com/open-mpi/ompi/commit/ac16970d21d21f529f1ec01ebe0520843227475b in order to get the intel compiler work with ompi Cheers, Gilles On 2015/01/16 17:29, Gilles Gouaillardet wrote: > George, > > i was unable to reproduce the hang with icc 14.0.3.174 and greater on

Re: [OMPI devel] Failures

2015-01-16 Thread Gilles Gouaillardet
George, i was unable to reproduce the hang with icc 14.0.3.174 and greater on a RHEL6 like distro. i was able to reproduce the opal_tree failure and found two possible workarounds : a) manually compile opal/class/opal_tree.lo *without* the -finline-functions flag b) update deserialize_add_tree_it

[OMPI devel] Failures

2015-01-15 Thread George Bosilca
Today's trunk compiled with icc fails to complete the check on 2 tests: opal_lifo and opal_tree. For opal_tree the output is: OPAL dss:unpack: got type 9 when expecting type 3 Failure : failed tree deserialization size compare SUPPORT: OMPI Test failed: opal_tree_t (1 of 12 failed) and opal_lif

Re: [OMPI devel] failures runing mpi4py testsuite, perhaps Comm.Split()

2007-07-11 Thread Lisandro Dalcin
On 7/11/07, George Bosilca wrote: The two errors you provide are quite different. The first one has been addresses few days ago in the trunk (https://svn.open-mpi.org/ trac/ompi/changeset/15291). If instead of the 1.2.3 you use anything after r15291 you will be safe in a threading case. Please

Re: [OMPI devel] failures runing mpi4py testsuite, perhaps Comm.Split()

2007-07-11 Thread George Bosilca
Lisandro, The two errors you provide are quite different. The first one has been addresses few days ago in the trunk (https://svn.open-mpi.org/ trac/ompi/changeset/15291). If instead of the 1.2.3 you use anything after r15291 you will be safe in a threading case. The second is different. T

[OMPI devel] failures runing mpi4py testsuite, perhaps Comm.Split()

2007-07-11 Thread Lisandro Dalcin
Ups, sended to wrong list, forwarded here... -- Forwarded message -- From: Lisandro Dalcin List-Post: devel@lists.open-mpi.org Date: Jul 11, 2007 8:58 PM Subject: failures runing mpi4py testsuite, perhaps Comm.Split() To: Open MPI Hello all, after a long time I'm here again. I