#1612 Some VTK tests fail when MPI was found
Metadata
Property | Value |
---|---|
Reported by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Reported at | Apr 10, 2015 11:49 |
Type | Bug Report |
Version | Git (pre2.4) [cmake] |
Operating System | Unspecified / All |
Last edited by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Last edited at | Apr 10, 2015 15:42 |
Closed by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Closed at | Apr 10, 2015 15:42 |
Closed in version | 2.4 |
Resolution | Fixed |
Comment | Fixed in |
dune-common 32ff3be | |
dune-grid 7ddce10 |
Description
Marian discovered that some of the VTK tests fail when building with MPI enabled. This happens because
- MPI is now enabled by default at configure time
- All VTK tests enable MPI by calling add_dune_mpi_flags()
- The VTK tests use YaspGrid, which is also parallel by default now.
The resulting error isn't overly helpful, stating that MPI routines may not be called before MPI_Init(). The problem in the VTK tests can simply be fixed by adding a call to MPIHelper::instance(), but I'd suggest also adding a check to the constructor of MPICollectiveCommunication and throwing an error in the constructor if MPI_Init wasn't called.