Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2019-04-06T00:15:10Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3749TrilinosCouplings build and test failures in the build Trilinos-atdm-white-ri...2019-04-06T00:15:10ZJames WillenbringTrilinosCouplings build and test failures in the build Trilinos-atdm-white-ride-cuda-9.2-release-debug-pt starting 2018-10-24*Created by: bartlettroscoe*
@trilinos/trilinoscouplings, @jwillenbring (Trilinos Framework Product Area Lead), @trilinos/muelu, @lucbv
## Next Action Status
Build and test errors were caused by merge of PR #3723 on 10/23/2018 th...*Created by: bartlettroscoe*
@trilinos/trilinoscouplings, @jwillenbring (Trilinos Framework Product Area Lead), @trilinos/muelu, @lucbv
## Next Action Status
Build and test errors were caused by merge of PR #3723 on 10/23/2018 that enabled this code by allowing the enable of `MueLu_ENABLE_Epetra=ON`. Next: Fix or disable these tests?
## Description
As shown [here](https://testing.sandia.gov/cdash-dev-view/viewBuildError.php?buildid=4103503), the TrilinosCouplings example files `IntrepidPoisson_Pamgen_EpetraAztecOO_main.cpp` and `IntrepidPoisson_Pamgen_Epetra_main.cpp` starting failing to compile in the build `Trilinos-atdm-white-ride-cuda-9.2-release-debug-pt` on 'ride' and 'white' starting on 2018-10-27 showing the build errors:
```
/home/jenkins/ride/workspace/Trilinos-atdm-white-ride-cuda-9.2-release-debug-pt/SRC_AND_BUILD/Trilinos/teuchos/core/src/Teuchos_RCP.hpp(288): error: a value of type "MueLu::Hierarchy<TrilinosCouplings::EpetraIntrepidPoissonExample::ST, int, int, KokkosClassic::DefaultNode::DefaultNodeType> *" cannot be used to initialize an entity of type "MueLu::EpetraOperator::Hierarchy *"
detected during instantiation of "Teuchos::RCP<T>::RCP(const Teuchos::RCP<T2> &) [with T=MueLu::EpetraOperator::Hierarchy, T2=MueLu::Hierarchy<TrilinosCouplings::EpetraIntrepidPoissonExample::ST, int, int, KokkosClassic::DefaultNode::DefaultNodeType>]"
/home/jenkins/ride/workspace/Trilinos-atdm-white-ride-cuda-9.2-release-debug-pt/SRC_AND_BUILD/Trilinos/trilinoscouplings/examples/scaling/IntrepidPoisson_Pamgen_EpetraAztecOO_main.cpp(259): here
1 error detected in the compilation of "/tmp/tmpxft_00005fee_00000000-6_IntrepidPoisson_Pamgen_EpetraAztecOO_main.cpp1.ii".
```
and
```
/home/jenkins/ride/workspace/Trilinos-atdm-white-ride-cuda-9.2-debug-pt/SRC_AND_BUILD/Trilinos/teuchos/core/src/Teuchos_RCP.hpp(288): error: a value of type "MueLu::Hierarchy<TrilinosCouplings::EpetraIntrepidPoissonExample::ST, int, int, KokkosClassic::DefaultNode::DefaultNodeType> *" cannot be used to initialize an entity of type "MueLu::EpetraOperator::Hierarchy *"
detected during instantiation of "Teuchos::RCP<T>::RCP(const Teuchos::RCP<T2> &) [with T=MueLu::EpetraOperator::Hierarchy, T2=MueLu::Hierarchy<TrilinosCouplings::EpetraIntrepidPoissonExample::ST, int, int, KokkosClassic::DefaultNode::DefaultNodeType>]"
/home/jenkins/ride/workspace/Trilinos-atdm-white-ride-cuda-9.2-debug-pt/SRC_AND_BUILD/Trilinos/trilinoscouplings/examples/scaling/IntrepidPoisson_Pamgen_Epetra_main.cpp(286): here
1 error detected in the compilation of "/tmp/tmpxft_00006693_00000000-6_IntrepidPoisson_Pamgen_Epetra_main.cpp1.ii".
```
This results in the test failures shown, for example, [here](https://testing.sandia.gov/cdash-dev-view/viewTest.php?onlyfailed&buildid=4103503):
* TrilinosCouplings_Example_Maxwell_MueLu_MPI_1
* TrilinosCouplings_Example_Maxwell_MueLu_MPI_4
Looking at the history of the TrilinosCouplings build on 'ride' [here](https://testing.sandia.gov/cdash-dev-view/index.php?project=Trilinos&date=2018-10-27&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-white-ride-cuda-9.2-debug-pt&field2=site&compare2=61&value2=ride&field3=subprojects&compare3=93&value3=TrilinosCouplings&field4=buildstarttime&compare4=83&value4=2018-09-26) we can see this these build failures started on 2018-10-24.
Looking at the git commits pulled that day shown [here](https://testing.sandia.gov/cdash-dev-view/viewNotes.php?buildid=4088183#!#note6), we see that the commits that likely caused by the PR #3722 with commits from @lucbv.
## Current Status on CDash
To see the current status of the build and tests for the current testing day and previous few days, click the below link:
* [TrilinosCouplings build and test results for 'Trilinos-atdm-white-ride-cuda-9.2-debug-pt' on 'ride'](https://testing.sandia.gov/cdash-dev-view/index.php?project=Trilinos&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Trilinos-atdm-white-ride-cuda-9.2-debug-pt&field2=site&compare2=61&value2=ride&field3=subprojects&compare3=93&value3=TrilinosCouplings&field4=buildstarttime&compare4=83&value4=10%20days%20ago)
NOTE: On above page, click on the "Start Time" column header to see the build results sorted by date.
## Steps to Reproduce
One should be able to reproduce these build errors on either 'white' or 'ride' by cloning the Trilinos git repo, checking out the 'develop' branch, creating a build directory, and then doing:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh cuda-9.2-release-debug
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_TrilinosCouplings=ON \
$TRILINOS_DIR
$ make NP=16
$ bsub -x -Is -q rhel7F -n 16 ctest -j16
```Initial cleanup of new ATDM builds of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1945several packages call exit() in the library2017-11-07T18:25:18ZJames Willenbringseveral packages call exit() in the library*Created by: nschloe*
Discussions of why calling `exit()` in production code go back as far as 2010; cf. https://software.sandia.gov/bugzilla/show_bug.cgi?id=4969. Unfortunately, many libraries still call `exit()`:
```
$ lintian * | g...*Created by: nschloe*
Discussions of why calling `exit()` in production code go back as far as 2010; cf. https://software.sandia.gov/bugzilla/show_bug.cgi?id=4969. Unfortunately, many libraries still call `exit()`:
```
$ lintian * | grep shlib-calls-exit
X: libtrilinos-zoltan12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_zoltan.so.12.12.1
X: libtrilinos-aztecoo12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_aztecoo.so.12.12.1
X: libtrilinos-muelu12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_muelu.so.12.12.1
X: libtrilinos-nox12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_noxepetra.so.12.12.1
X: libtrilinos-stokhos12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_stokhos_muelu.so.12.12.1
X: libtrilinos-galeri12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_galeri-epetra.so.12.12.1
X: libtrilinos-epetraext12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_epetraext.so.12.12.1
X: libtrilinos-shylu12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_shylu.so.12.12.1
X: libtrilinos-pamgen12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_pamgen.so.12.12.1
X: libtrilinos-ml12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_ml.so.12.12.1
X: libtrilinos-triutils12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_triutils.so.12.12.1
X: libtrilinos-ifpack12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_ifpack.so.12.12.1
X: libtrilinos-pliris12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_dpliris.so.12.12.1
X: libtrilinos-trilinoscouplings12: shlib-calls-exit usr/lib/x86_64-linux-gnu/libtrilinos_trilinoscouplings.so.12.12.1
```
Would be great to see some progress here.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/19TrilinosCouplings/STKClassic: ‘FieldBase’ does not name a type2016-06-26T03:27:31ZJames WillenbringTrilinosCouplings/STKClassic: ‘FieldBase’ does not name a type*Created by: nschloe*
**Next Action Status:**
STKClassic support in TrilinosCouplings is now always disabled by default (even if TrilinosCouplings and STKClassic are both enabled). Next: Fix or remove code dependent on STKClassic?
**...*Created by: nschloe*
**Next Action Status:**
STKClassic support in TrilinosCouplings is now always disabled by default (even if TrilinosCouplings and STKClassic are both enabled). Next: Fix or remove code dependent on STKClassic?
**Description:**
When configuring Trilinos with
```
cmake \
-DCMAKE_INSTALL_PREFIX:PATH=/opt/trilinos/ \
-DCMAKE_BUILD_TYPE:STRING=Debug \
-DCMAKE_C_COMPILER=mpicc \
-DCMAKE_CXX_COMPILER=mpicxx \
-DCMAKE_Fortran_COMPILER=mpif90 \
-DBUILD_SHARED_LIBS:BOOL=ON \
-DCMAKE_SKIP_RPATH:BOOL=ON \
-DTrilinos_INSTALL_INCLUDE_DIR:PATH=include/trilinos/ \
-DTrilinos_ENABLE_DEVELOPMENT_MODE:BOOL=OFF \
-DTrilinos_ENABLE_ALL_PACKAGES:BOOL=ON \
-DTrilinos_ENABLE_SECONDARY_STABLE_CODE:BOOL=ON \
-DTrilinos_ASSERT_MISSING_PACKAGES:BOOL=OFF \
-DTrilinos_ENABLE_MeshingGenie:BOOL=ON \
-DTrilinos_ENABLE_ForTrilinos:BOOL=OFF \
-DTrilinos_ENABLE_Optika:BOOL=OFF \
-DTrilinos_ENABLE_Phdmesh:BOOL=ON \
-DTrilinos_ENABLE_PyTrilinos:BOOL=OFF \
-DTrilinos_ENABLE_STKSearch:BOOL=OFF \
-DTrilinos_ENABLE_STKTransfer:BOOL=OFF \
-DTrilinos_ENABLE_ShyLU:BOOL=ON \
-DTrilinos_ENABLE_Trios:BOOL=ON \
-DPanzer_ENABLE_EXPLICIT_INSTANTIATION:BOOL=ON \
-DSEACASExodus_ENABLE_MPI:BOOL=OFF \
-DTrilinos_ENABLE_EXAMPLES:BOOL=ON \
-DTrilinos_ENABLE_TESTS:BOOL=ON \
-DPiro_ENABLE_TESTS:BOOL=OFF \
-DShyLU_ENABLE_TESTS:BOOL=OFF \
-DTPL_ENABLE_BinUtils:BOOL=ON \
-DTPL_ENABLE_Boost:BOOL=ON \
-DTPL_ENABLE_MATLAB:BOOL=OFF \
-DTPL_ENABLE_Matio:BOOL=OFF \
-DTPL_ENABLE_MPI:BOOL=ON \
-DTPL_ENABLE_MUMPS:BOOL=ON \
-DTPL_ENABLE_Netcdf:BOOL=ON \
-DTPL_ENABLE_ParMETIS:BOOL=OFF \
-DTPL_ENABLE_Scotch:BOOL=ON \
-DTPL_Scotch_INCLUDE_DIRS:PATH=/usr/include/scotch/ \
-DTPL_ENABLE_Eigen:BOOL=ON \
-DTPL_Eigen_INCLUDE_DIRS:PATH=/usr/include/eigen3/ \
-DTPL_ENABLE_TBB:BOOL=ON \
-DTPL_ENABLE_X11:BOOL=OFF \
-DTPL_ENABLE_Zlib:BOOL=ON \
../../source-upstream/
```
(perhaps there is this can be trimmed down), one gets the compilation error
```
[...]
[100%] Building CXX object packages/trilinoscouplings/examples/scaling/CMakeFiles/TrilinosCouplings_Example_Poisson_STKclassic.dir/example_Poisson_stkclassic.cpp.o
In file included from /home/nschloe/software/trilinos/source-upstream/packages/trilinoscouplings/examples/scaling/example_Poisson_stkclassic.cpp:135:0:
/home/nschloe/software/trilinos/source-upstream/packages/stk/stk_classic/stk_mesh/stk_mesh/fem/../../stk_mesh/base/FieldData.hpp:79:30: error: ‘FieldBase’ does not name a type
bool field_data_valid( const FieldBase & f ,
[...]
```