Failures on sid buildbot
Issue #597
resolved
Comments (13)
-
reporter
-
Yes, PETSc 3.6.2 has been uploaded to Debian unstable and I have installed it on the sid buildbot. The MUMPS package in Debian is version 4.10 and not updated since 2011.
-
reporter
Are you sure that MUMPS on sid is not installed by PETSc? That would be MUMPS 5, https://bitbucket.org/petsc/petsc/commits/d341cd04ead25786cb579bd428dce3b9509eec8a.
-
reporter
Anyway removing some silly "patches" d0b56bd helped there.
-
@blechta - Yes, both PETSc and MUMPS are installed as Debian packages on the sid buildbot. Nothing is installed by PETSc in the Debian package. If you think this is a bug in this version of MUMPS, I can remove PETSc from this buildbot and we will likely end up with the original problems of this bug report.
-
reporter
No need to do that. I was just curious if this behaviour is caused by MUMPS 5 in PETSc 3.6.
-
reporter
-
assigned issue to
Jan Blechta
- changed milestone to 1.7
Branch
jan/petsc-3.7-updateswill fix both sid and mpich buildbot.MUMPS workaround is no longer needed. Let MUMPS decides about the best reordering algorithm freely.
Let me figure out the SuperLU_dist situation later. Possibly related (but rather not): https://bitbucket.org/petsc/petsc/commits/ceeba3afeff0c18262ed13ef92e2508ca68b0ecf, http://lists.mcs.anl.gov/pipermail/petsc-users/2015-August/026671.html.
-
assigned issue to
-
reporter
Another possibility:
PCFactorSetShiftType,PCFactorSetShiftAmountinPETScLUSolver.cpp. -
reporter
SuperLU_dist problem reported to PETSc http://lists.mcs.anl.gov/pipermail/petsc-users/2015-November/027635.html
-
reporter
- changed status to resolved
sid is now green
-
I've raised this before with PETSc devs too. Apparently SuperLU_dist does very little pivoting, so can have problems with mixed/saddle point problems.
-
reporter
Could be. And non-determinism in parallel could come from unseeded random generators in ParMETIS. Need to check if its configurable. I think I've seen it somewhere.
-
- removed milestone
Removing milestone: 1.7 (automated comment)
- Log in to comment
The original problem 1. and 2. were somehow resolved. Now we have instead problems with bad numerical stability in MUMPS. Maybe it's new major release 5.