David: I'll patch petsc-maint (v3.7), then merge it to petsc-master. It might take 1-2 days for regression tests.
Hong On Tue, Sep 20, 2016 at 2:01 PM, Hong <hzh...@mcs.anl.gov> wrote: > >> David : >> This is a bug in PETSc. A change >> $ git diff ../../../pc/impls/factor/cholesky/cholesky.c >> diff --git a/src/ksp/pc/impls/factor/cholesky/cholesky.c >> b/src/ksp/pc/impls/factor/cholesky/cholesky.c >> index 953d551..cc28369 100644 >> --- a/src/ksp/pc/impls/factor/cholesky/cholesky.c >> +++ b/src/ksp/pc/impls/factor/cholesky/cholesky.c >> @@ -141,9 +141,7 @@ static PetscErrorCode PCSetUp_Cholesky(PC pc) >> >> ierr = MatCholeskyFactorNumeric(((PC_Factor*)dir)->fact,pc->pmat,&( >> (PC_Factor*)dir)->info);CHKERRQ(ierr); >> ierr = MatFactorGetError(((PC_Factor*)dir)->fact,&err);CHKERRQ(ierr >> ); >> - if (err) { /* FactorNumeric() fails */ >> - pc->failedreason = (PCFailedReason)err; >> - } >> + pc->failedreason = (PCFailedReason)err; >> } >> >> fixed the problem. I'll fix this problem in petsc-release, including >> other routines. >> Thanks for reporting the bug and sending matrix.dat. Let us know whenever >> you encounter problem using PETSc. >> > > > OK, great, thanks for the fix. > > Will this fix be included in the next patch release of 3.7? > > Thanks, > David > > > >