dolfin team mailing list archive

[Johannes Ring <johannr@xxxxxxxxx>]

This failure was expected and not Martin's fault.The problem is the
stokes-iterative C++ demo, which is problematic when run in parallel
(parallel testing has been turned off on this buildbot slave until
now).

I have done some manual testing with two and up to five processes and
the demo fails only (but not always) when run with three or five
processes. Sometimes I get a segmentation violation:

[1]PETSC ERROR:
------------------------------------------------------------------------
[1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
probably memory access out of range
[1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[1]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[1]PETSC
ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to
find memory corruption errors
[1]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[1]PETSC ERROR: to get more information on the crash.
[1]PETSC ERROR: --------------------- Error Message
------------------------------------
[1]PETSC ERROR: Signal received!
[1]PETSC ERROR:
------------------------------------------------------------------------

Other times I get this error:

Warning -- row partitioning does not line up! Partitioning incomplete!
[2]PETSC ERROR: MatHYPRE_IJMatrixCreate() line 76 in src/dm/da/utils/mhyp.c
[2]PETSC ERROR: PCSetUp_HYPRE() line 112 in src/ksp/pc/impls/hypre/hypre.c
[2]PETSC ERROR: PCSetUp() line 795 in src/ksp/pc/interface/precon.c
[2]PETSC ERROR: KSPSetUp() line 237 in src/ksp/ksp/interface/itfunc.c
[2]PETSC ERROR: KSPSolve() line 353 in src/ksp/ksp/interface/itfunc.c
Process 2: Soln norm: 0

Any ideas? Is it a bug in DOLFIN? The demo works fine in parallel when
using Trilinos instead of PETSc.

BTW, the slave was recently upgraded to Ubuntu Oneiric and all
dependencies are installed from the official package archive (except
MTL4).

Johannes

On Mon, Oct 24, 2011 at 1:03 PM,  <buildbot@xxxxxxxxxx> wrote:
> The Buildbot has detected a new failure of dolfin-oneiric-i386 on FEniCS Buildbot.
> Full details are available at:
>  http://fenicsproject.org:8080/builders/dolfin-oneiric-i386/builds/4
>
> Buildbot URL: http://fenicsproject.org:8080/
>
> Buildslave for this Build: oneiric-i386
>
> Build Reason:
> Build Source Stamp: HEAD
> Blamelist: Martin Sandve Aln=C3=A6s
>
> BUILD FAILED: failed dolfin check
>
> sincerely,
>  -The Buildbot
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp
>