[petsc-dev] error in Jenkins but not nightly

Smith, Barry F. bsmith at mcs.anl.gov
Mon Jun 10 11:29:55 CDT 2019

I've noticed this issue with Jenkins tests recently but don't see it in next nightly builds


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