Dear PETSc users,
The patch release petsc-3.13.2 is now available for download,
with change list at 'PETSc-3.13 Changelog'
http://www.mcs.anl.gov/petsc/download/index.html
Satish
Jacob Faibussowitsch writes:
> 2. (More a question for Jed) If I am using Jeds docker image anyways and we
> have CI/CD builds also using his docker images (correct me if I am wrong
> here) and a valgrind build in stage 3 why not include those build arguments
> in the MPICH included in the
If using docker - I would think you should be able to make changes [as you
need] and save them [as your own docker image file].
And wrt PETSC-CI, only stage-1 tests use the docker images.
A single image for the whole CI doesn't make any sense. [we test different
OSes, different compilers,
> You can verify with: mpichversion
Yes you’re right. Here is what this produces for me
MPICH Version: 3.3.2
MPICH Release date: Tue Nov 12 21:23:16 CST 2019
MPICH Device: ch3:sock
MPICH configure:--disable-wrapper-rpath --with-device=ch3:sock
MPICH CC: gcc
It's not the most satisfying solution but you can also pretty quickly
generate and use suppression files to at least de-clutter the output:
https://valgrind.org/docs/manual/manual-core.html#manual-core.suppress
Am Di., 2. Juni 2020 um 18:59 Uhr schrieb Satish Balay via petsc-dev <
> MPICH need to be built with the option --enable-g=meminit for it to be
> valgrind clean.
I see. Two questions:
1. I am using Jeds docker image for MPICH (actually this is the main reason for
using Jeds image, as configuring and building MPICH takes an absolute age on
docker), will this
MPICH need to be built with the option --enable-g=meminit for it to be valgrind
clean.
--download-mpich does this [among other things that are useful during software
developement]. Pre-configured MPICH is not likely to do this.
You can verify with: mpichversion
You can prebuild MPICH using
Yes I am using the pre-loaded MPICH from the docker image. Further proof from
configure
#define PETSC_HAVE_MPICH_NUMVERSION 30302300
#define PETSC_HAVE_MPIEXEC_ENVIRONMENTAL_VARIABLE MPIR_CVAR_CH3
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On
I guess Jacob already used MPICH, since MPIDI_CH3_EagerContigShortSend() is
from MPICH.
--Junchao Zhang
On Tue, Jun 2, 2020 at 9:38 AM Satish Balay via petsc-dev <
petsc-dev@mcs.anl.gov> wrote:
> use --download-mpich for valgrind.
>
>
use --download-mpich for valgrind.
https://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
Satish
On Tue, 2 Jun 2020, Karl Rupp wrote:
> Hi Jacob,
>
> the recommendation in the past was to use MPICH as it is (was?)
> valgrind-clean. Which MPI do you use? OpenMPI used to have these kinds
10 matches
Mail list logo
