[petsc-dev] error in Jenkins but not nightly

Balay, Satish balay at mcs.anl.gov
Mon Jun 10 11:36:39 CDT 2019

Ok - this must be the result of having prebuilt external packages used
for jenkins - for both maint/master [while master changes with updates
to use newer versions]

I think I might have to split maint/master part of prebuild external
packages - and upgrade the master version [as master gets updated with
newer versions].

BTW: the following merge to master is the trigger

commit 5363a1905b822d8ec4152b9a6fcd1bc5ecfdfb35 (HEAD -> master, origin/master, origin/HEAD)
Merge: 5604a6f22e 5dc3e8b4b9
Author: Satish Balay <balay at mcs.anl.gov>
Date:   Sun Jun 9 09:22:52 2019 -0500

    Merge branch 'pr1723/tappel/extend-mumps-parameters/master' [PR #1723]


On Mon, 10 Jun 2019, Smith, Barry F. via petsc-dev wrote:

> I've noticed this issue with Jenkins tests recently but don't see it in next nightly builds
> https://petsc-dev.org/jenkins/blue/organizations/jenkins/pj02%2Farch-jenkins-linux-gcc-pkgs-opt/detail/PR-1773/1/tests
> perhaps related to last MUMPS release? One number seems oddly large 
> ICNTL(38) (estimated compression rate of LU factors): 333
> ---
> > ICNTL(38) (estimated compression rate of LU factors): 0
> Perhaps the test is never run in nightly but only in Jenkins, so the output files were not updated?
> Or a bad report from MUMPS due to memory initialize issues? Who knows

More information about the petsc-dev mailing list