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
