Hi Gilles,
On 13/07/16 08:01 PM, Gilles Gouaillardet wrote:
Eric,
OpenMPI 2.0.0 has been released, so the fix should land into the v2.x
branch shortly.
ok, thanks again.
If i understand correctly, you script download/compile OpenMPI and then
download/compile PETSc.
More precisely, for Op
Thanks Ralph,
It is now *much* better: all sequential executions are working... ;)
but I still have issues with a lot of parallel tests... (but not all)
The SHA tested last night was c3c262b.
http://www.giref.ulaval.ca/~cmpgiref/dernier_ompi/2016.07.14.01h20m32s_config.log
Here is what is the
This looks like a new error -- something is potentially going wrong in
MPI_Request_free (or perhaps the underlying progress invocation invoked by
MPI_Request_free).
I think cloning at that time and running tests is absolutely fine.
We tend to track our bugs in Github issues, so if you'd like to
Hi All,
Doing quick test with rand()/srand() I found that MPI_Init() seems to be
calling a function in their family that is affecting the values in the user
application. Please see below my simple test and the results. Yes, moving the
second call to srand() after MPI_init() solves the problem
We have talked about this on the weekly calls, but for those of you who have
not been able to attend, here's a summary of our expected plans with git
branches, github repos, etc.:
1. v2.0.0 has been released. Yay!
2. A picture is worth 1,000 words: below is the git branching plan for the v2.x
