Developers --
A request: when you have a commit that fixes a user-reported issue, please
thank the user in the commit message (e.g., "Thanks to Joe Shmoe for reporting
the issue."). It's good for the community, and it also *really* helps us write
the NEWS file when it comes time for release.
On Mar 3, 2017, at 3:05 AM, Gilles Gouaillardet wrote:
>
> bottom line, MPI tasks that run on the same node mpirun was invoked on inherit
> the core file size limit from mpirun, whereas tasks that run on the other node
> use the default core file size limit.
I am not sure
Isn't this supposed to be part of cluster 101?
I would rather add it to our faq, maybe in a slightly more generic way (not
only focused towards 'ulimit - c'. Otherwise we will be bound to define
what is forwarded and what is not, and potentially creates chaos for
knowledgeable users (that know
Thanks Paul,
It looks like we (indirectly) call MPI_Abort() when the argument is invalid.
That would explain the counter intuitive error message
Cheers,
Gilles
Paul Kapinos wrote:
>Dear Open MPI developer,
>please take a look at the attached 'hello MPI world'
Dear Open MPI developer,
please take a look at the attached 'hello MPI world' file.
We know that it contain an error (you should never put '1476395012' into
MPI_Init_thread() call! It was a typo, initially...) BUT, see what happens if
you compile it:
$ mpif90 -g mpihelloworld.f90
$ ./a.out
Folks,
this is a follow-up on
https://www.mail-archive.com/users@lists.open-mpi.org//msg30715.html
on my cluster, the core file size is 0 by default, but it can be set to
unlimited by any user.
i think this is a pretty common default.
$ ulimit -c
0
$ bash -c 'ulimit -c'
0
$ mpirun -np