Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2019-06-08T15:27:25Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/5029TrilinosCouplings: Build error (missing header file)2019-06-08T15:27:25ZJames WillenbringTrilinosCouplings: Build error (missing header file)*Created by: mhoemmen*
## Bug Report
@trilinos/trilinoscouplings
### Description
```
.../Trilinos/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:156:18: error: ‘PseudoBlockCGSolMgr’ in namespace ‘Belos’ does not name ...*Created by: mhoemmen*
## Bug Report
@trilinos/trilinoscouplings
### Description
```
.../Trilinos/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:156:18: error: ‘PseudoBlockCGSolMgr’ in namespace ‘Belos’ does not name a template type
const Belos::PseudoBlockCGSolMgr<Sc, V, O>* cg_solver =
^
.../Trilinos/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:158:9: error: ‘cg_solver’ was not declared in this scope
if (cg_solver != 0)
^
```https://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/3551TrilinosCouplings_ml_nox_1Delasticity_example_MPI_4 test failing in Trilinos-...2018-11-30T03:19:30ZJames WillenbringTrilinosCouplings_ml_nox_1Delasticity_example_MPI_4 test failing in Trilinos-atdm-white-ride-cuda-9.2-debug-pt build*Created by: bartlettroscoe*
CC: @trilinos/trilinoscouplings , @jwillenbring (Trilinos Framework Product Area Lead), @fryeguy52
## Next Action Status
PR #3568 merged on 10/5/2018 fixed this test as shown in the build on 10/6/2018...*Created by: bartlettroscoe*
CC: @trilinos/trilinoscouplings , @jwillenbring (Trilinos Framework Product Area Lead), @fryeguy52
## Next Action Status
PR #3568 merged on 10/5/2018 fixed this test as shown in the build on 10/6/2018.
## Description
The test `TrilinosCouplings_ml_nox_1Delasticity_example_MPI_4` is failing in the build `Trilinos-atdm-white-ride-cuda-9.2-debug-pt ` on 'white' and 'ride' as shown [here](https://testing.sandia.gov/cdash-dev-view/testDetails.php?test=55725442&build=3998269) which shows the failing output:
```
5001
5001
5001
5001
TrilinosCouplings_ml_nox_1Delasticity_example.exe: /home/jenkins/white/workspace/Trilinos-atdm-white-ride-cuda-9.2-debug-pt/SRC_AND_BUILD/Trilinos/packages/trilinoscouplings/examples/ml/NonlinML/FiniteElementProblem.cpp:218: bool FiniteElementProblem::evaluate(FillType, const Epetra_Vector*, Epetra_Vector*, Epetra_RowMatrix*): Assertion `ierr' failed.
[white27:17997] *** Process received signal ***
[white27:17997] Signal: Aborted (6)
[white27:17997] Signal code: (-6)
[white27:17997] [ 0] [0x3fffa9850478]
[white27:17997] TrilinosCouplings_ml_nox_1Delasticity_example.exe: /home/jenkins/white/workspace/Trilinos-atdm-white-ride-cuda-9.2-debug-pt/SRC_AND_BUILD/Trilinos/packages/trilinoscouplings/examples/ml/NonlinML/FiniteElementProblem.cpp:218: bool FiniteElementProblem::evaluate(FillType, const Epetra_Vector*, Epetra_Vector*, Epetra_RowMatrix*): Assertion `ierr' failed.
[white27:17998] *** Process received signal ***
[white27:17998] Signal: Aborted (6)
[white27:17998] Signal code: (-6)
[white27:17998] [ 0] [0x3fff7ce70478]
[white27:17998] [ 1] TrilinosCouplings_ml_nox_1Delasticity_example.exe: /home/jenkins/white/workspace/Trilinos-atdm-white-ride-cuda-9.2-debug-pt/SRC_AND_BUILD/Trilinos/packages/trilinoscouplings/examples/ml/NonlinML/FiniteElementProblem.cpp:218: bool FiniteElementProblem::evaluate(FillType, const Epetra_Vector*, Epetra_Vector*, Epetra_RowMatrix*): Assertion `ierr' failed.
[white27:17999] *** Process received signal ***
[white27:17999] Signal: Aborted (6)
[white27:17999] Signal code: (-6)
[white27:17999] [ 0] [0x3fffa4920478]
[white27:17999] [ 1] /lib64/libc.so.6(abort+0x2b4)[0x3fff97081f94]
[white27:17999] [ 2] TrilinosCouplings_ml_nox_1Delasticity_example.exe: /home/jenkins/white/workspace/Trilinos-atdm-white-ride-cuda-9.2-debug-pt/SRC_AND_BUILD/Trilinos/packages/trilinoscouplings/examples/ml/NonlinML/FiniteElementProblem.cpp:218: bool FiniteElementProblem::evaluate(FillType, const Epetra_Vector*, Epetra_Vector*, Epetra_RowMatrix*): Assertion `ierr' failed.
[white27:18000] *** Process received signal ***
[white27:18000] Signal: Aborted (6)
[white27:18000] Signal code: (-6)
...
```
This is an important build because we are targeting this build on 'white' and 'ride' as a Trilinos CUDA PR testing build (see #2464 ). However, the SPARC and EMPIRE ATDM Trilinos builds don't enable TrilinosCouplings so we could just disable this test and not impact ATDM at all.
## 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-debug
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnvAllPtPackages.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/2786TrilinosCouplings build failure2018-06-21T23:29:20ZJames WillenbringTrilinosCouplings build failure*Created by: ibaned*
<!---
Provide a general summary of the issue in the Title above. If this issue
pertains to a particular package in Trilinos, it's worthwhile to start the
title with "PackageName: ".
-->
<!---
Note that any...*Created by: ibaned*
<!---
Provide a general summary of the issue in the Title above. If this issue
pertains to a particular package in Trilinos, it's worthwhile to start the
title with "PackageName: ".
-->
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/muelu
@trilinos/framework @maherou ~~There is no GitHub team for TrilinosCouplings~~
Edit: there is now, not sure if I just missed it
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
## Expectations
<!---
Tell us what you think should happen, how you think things should work, what
you would like to see in the documentation, etc.
-->
TrilinosCouplings should compile without error
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
```
packages/trilinoscouplings/examples/scaling/example_Maxwell.cpp(152): catastrophic error: cannot open source file "MueLu_AztecEpetraOperator.hpp"
#include <MueLu_AztecEpetraOperator.hpp>
```
## Motivation and Context
<!---
How has this expectation failure affected you? What are you trying to
accomplish? Why do we need to address this? What does it have to do with
anything? Providing context helps us come up with a solution that is most
useful in the real world.
-->
This is preventing snapshotting a new Kokkos version
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/2281Warnings-as-errors need cleaned up2018-02-23T19:44:45ZJames WillenbringWarnings-as-errors need cleaned up*Created by: prwolfe*
<!---
Provide a general summary of the issue in the Title above. If this issue
pertains to a particular package in Trilinos, it's worthwhile to start the
title with "PackageName: ".
-->
All three builds that...*Created by: prwolfe*
<!---
Provide a general summary of the issue in the Title above. If this issue
pertains to a particular package in Trilinos, it's worthwhile to start the
title with "PackageName: ".
-->
All three builds that use watnings-as-errors are showing 50+ failures. We need to look into these to support customers that use this. See https://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=3400360
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/Trilinos Couplings 3 errors from 2 files
(packages/trilinoscouplings/src/ml/NonlinML/nlnml_preconditioner_utils.cpp) has unused varliables
(packages/trilinoscouplings/src/ml/NonlinML/nlnml_preconditioner1.cpp) due to initialization order.
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
## Expectations
<!---
Tell us what you think should happen, how you think things should work, what
you would like to see in the documentation, etc.
-->
These warnings/errors should be resolved and the changes set as pull requests into develop to support Sierra and other codes. When those pull requests are merged the ticket should be closed.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Warnings-as-errors builds fail on the above conditions
## Motivation and Context
<!---
How has this expectation failure affected you? What are you trying to
accomplish? Why do we need to address this? What does it have to do with
anything? Providing context helps us come up with a solution that is most
useful in the real world.
-->
## Definition of Done
<!---
Tell us what needs to happen. If necessary, give us a task list along the
lines of:
- [ ] First do this.
- [ ] Then do that.
- [ ] Also this other thing.
-->
## Possible Solution
<!---
Not obligatory, but suggest a fix for the bug or documentation, or suggest
ideas on how to implement the addition or change.
-->
## Steps to Reproduce
<!---
Provide a link to a live example, or an unambiguous set of steps to reproduce
this issue. Include code to reproduce, if relevant.
1. Do this.
1. Do that.
1. Shake fist angrily at computer.
-->
## Your Environment
<!---
Include relevant details about your environment such that we can replicate this
issue.
-->
- **Relevant repo SHA1s:**
- **Relevant configure flags or configure script:**
- **Operating system and version:**
- **Compiler and TPL versions:**
## Related Issues
<!---
If applicable, let us know how this bug is related to any other open issues:
-->
* Blocks
* Is blocked by
* Follows
* Precedes
* Related to
* Part of
* Composed of
## Additional Information
<!---
Anything else that might be helpful for us to know in addressing this issue:
* Configure log file:
* Build log file:
* Test log file:
* When was the last time everything worked (date/time; SHA1s; etc.)?
* What did you do that made the bug rear its ugly head?
* Have you tried turning it off and on again?
-->https://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/690AllowPadding and WithoutInitializing moving to Kokkos namespace change downst...2017-10-27T04:10:00ZJames WillenbringAllowPadding and WithoutInitializing moving to Kokkos namespace change downstream Trilinos code accordingly*Created by: mhoemmen*
Kokkos/develop has moved AllowPadding and WithoutInitializing out of the Kokkos::Experimental namespace, into the Kokkos namespace. Once this gets moved into Kokkos/master and snapshotted into Trilinos, change Tr...*Created by: mhoemmen*
Kokkos/develop has moved AllowPadding and WithoutInitializing out of the Kokkos::Experimental namespace, into the Kokkos namespace. Once this gets moved into Kokkos/master and snapshotted into Trilinos, change Trilinos downstream code accordingly.
https://github.com/kokkos/kokkos/issues/325
@trilinos/tpetra
@trilinos/stokhos
@trilinos/sacado
@trilinos/shylu
@trilinos/stk
Tpetra-backloghttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1301MueLu: undefined references2017-05-10T15:59:53ZJames WillenbringMueLu: undefined references*Created by: lxmota*
When compiling Albany I get the errors:
/home/amota/LCM/trilinos-install-serial-gcc-release/lib/libmuelu-adapters.so.12.11: undefined reference to `MueLu::HierarchyManager<double, int, int, Kokkos::Compat::Kokkos...*Created by: lxmota*
When compiling Albany I get the errors:
/home/amota/LCM/trilinos-install-serial-gcc-release/lib/libmuelu-adapters.so.12.11: undefined reference to `MueLu::HierarchyManager<double, int, int, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Serial, Kokkos::HostSpace> >::exportCount_'
/home/amota/LCM/trilinos-install-serial-gcc-release/lib/libmuelu-adapters.so.12.11: undefined reference to `MueLu::HierarchyManager<double, int, int, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Serial, Kokkos::HostSpace> >::ctorCount_'
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/895Resolve build failures for checkin-test-sems.sh MPI_RELEASE_DEBUG_SHARED_PT b...2016-12-10T03:20:11ZJames WillenbringResolve build failures for checkin-test-sems.sh MPI_RELEASE_DEBUG_SHARED_PT build on OSX*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/stokos, @trilinos/muelu, @trilinos/stk, @trilinos/zoltan
**Description:**
The [checkin-test-sems.sh](https://github.com/trilinos/Trilinos/wiki/Policies-%7C-Safe-C...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/stokos, @trilinos/muelu, @trilinos/stk, @trilinos/zoltan
**Description:**
The [checkin-test-sems.sh](https://github.com/trilinos/Trilinos/wiki/Policies-%7C-Safe-Checkin-Testing) default build MPI_RELEASE_DEBUG_SHARED_PT was set up to use the GCC 5.3.0 compiler stack as discussed in #482. The goal was to provide a uniform build between Linux and OSX machines. That failed very badly because while things built and ran just fine on Linux, the code did not even build with the same compilers and TPLs on OSX. However, it would still be very useful to have a standard PT pre-push CI build working on OSX for OSX developers. A recent Trilinos survey shown here:
* https://docs.google.com/forms/d/13JyOK0dMdK0tfiXasv5fAkf8gtL5_JWL5vUgFS8e2W0/edit#responses
showed that nearly 32% of Trilinos developers consider OSX to be the **primary** development platform for Trilinos. In addition, 16% said they did not have access to a SNL RHEL 6 COE with the SEMS env to test and push from.
Therefore, one strategy to accommodate these Trilinos developers is to allow them to push directly from OSX. The full details of how such a system would work is beyond the scope of this story but the first step would be get an initial passing build and test suite for Trilinos for this build.
Currently the Trilinos PT packages don't even build for this MPI_RELEASE_DEBUG_SHARED_PT build and there were many test failures for some packages that did not have build failures.
To demonstrate, I ran:
```
$ ./checkin-test-sems.sh --enable-all-packages=on --local-do-all
```
on the Trilinos version:
```
*** Base Git Repo: Trilinos
c6eb35a [Tue Nov 29 16:18:17 2016 -0500] <rppawlo@sandia.gov>
Phalanx: update for kokkos TaskPolicy --> TaskScheduler
```
from an OSX machine that had the SEMS env mounted (gaia).
I then ran `make dashbaord` in the MPI_RELEASE_DEBUG_SHARED_PT build directory and it uploaded the results to:
* http://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=2634842
This shows 2 build failures in many Trilinos packages (I think CTest is reporting this incorrectly) but there was really only build failures in the STK package and the ROL package. The build failures in the STK package where in the library and therefore none of the STK tests were run. The build failure in the ROL package was for a single example that caused 58 tests not to run. The remaining 61 ROL tests all passed.
Other than these ROL test failures, there were test falures in the packages TrilinosCouplings, Stokhos, MueLu, and Zoltan shown here:
* http://testing.sandia.gov/cdash/viewTest.php?onlyfailed&buildid=2634842
There is no sense listing out the tests in detail in this Issue but one can reproduce these failures for any package `<PKG>` on OSX by checking out the Trilinos version c6eb35a (or the current version) and then running:
```
./checkin-test-sems.sh --enable-packages=<PKG> --local-do-all
```
If we want to allow Trilinos developers to push from OSX, then we need to clean up these failures and then we can talk about a sane and workable process to allow Trilinos developers to push from either Linux and OSX. It will be more complicated and will require things like a [`--compare-to-control-build`](https://github.com/TriBITSPub/TriBITS/issues/152) option for the checkin-test.py script but I think that is a very realistic goal.
Is there energy and interest to fix these problems on OSX?
Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/896 TrilinosCouplings_Poisson2D_pn=4_tpetra_MPI_1 failing in current CI build2016-12-01T20:01:39ZJames Willenbring TrilinosCouplings_Poisson2D_pn=4_tpetra_MPI_1 failing in current CI build*Created by: bartlettroscoe*
**CC:** @trilinos/framework@, @csiefer2
**Description:**
It appears that the commits:
```
commit f76752c69bf5231f98e0ac77436dce44e15a57aa
Author: Chris Siefert <csiefer@sandia.gov>
Date: Wed N...*Created by: bartlettroscoe*
**CC:** @trilinos/framework@, @csiefer2
**Description:**
It appears that the commits:
```
commit f76752c69bf5231f98e0ac77436dce44e15a57aa
Author: Chris Siefert <csiefer@sandia.gov>
Date: Wed Nov 30 15:30:33 2016 -0700
TrilinosCouplings: Debugging gunk for one-grid
M packages/trilinoscouplings/examples/scaling/example_Poisson2D_pn_tpetra.cpp
commit e7ba523edb56fd067366fe1455903cedb2ee89a0
Author: Chris Siefert <csiefer@sandia.gov>
Date: Wed Nov 30 15:30:05 2016 -0700
MueLu: Adding support for block relaxation on coarse grids
M packages/muelu/src/Interface/MueLu_ParameterListInterpreter_def.hpp
```
broke the test TrilinosCouplings_Poisson2D_pn=4_tpetra_MPI_1 in the new CI build as shown here:
* http://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=2636238
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/884TrilinosCouplings Scaling examples fails to build in CI build2016-11-29T18:48:25ZJames WillenbringTrilinosCouplings Scaling examples fails to build in CI build*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/intrepid2
**Description:**
The TrilinosCouplings example example_Poisson2D_pn_tpetra.cpp currently fails to build as shown here:
* http://testing.sandia.gov/c...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/intrepid2
**Description:**
The TrilinosCouplings example example_Poisson2D_pn_tpetra.cpp currently fails to build as shown here:
* http://testing.sandia.gov/cdash/viewBuildError.php?buildid=2632716
which shows:
```
trilinoscouplings/examples/scaling/example_Poisson2D_pn_tpetra.cpp:102:40: fatal error: Intrepid2_FieldContainer.hpp: No such file or directory
```
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/837TrilinosCouplings: fenl_ensemble.hpp errors2016-11-15T23:11:41ZJames WillenbringTrilinosCouplings: fenl_ensemble.hpp errors*Created by: sagitter*
Hi all.
`fenl` example does not compile with following error:
```
In file included from /builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/main_e...*Created by: sagitter*
Hi all.
`fenl` example does not compile with following error:
```
In file included from /builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/main_ensemble.cpp:9:0:
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:164:9: error: 'GetMeanValsFunc' is not a class template
class GetMeanValsFunc< Kokkos::View< Sacado::MP::Vector<Storage>*,
^
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:248:15: error: 'SolverManager' in namespace 'Belos' does not name a type
apply(const Belos::SolverManager<Sc,V,O>& solver) {
^
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:248:22: error: ISO C++ forbids declaration of 'parameter' with no type [-fpermissive]
apply(const Belos::SolverManager<Sc,V,O>& solver) {
^
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:248:35: error: expected ',' or '...' before '<' token
apply(const Belos::SolverManager<Sc,V,O>& solver) {
^
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp: In static member function 'static std::vector<int, std::allocator<int> > Kokkos::Example::ExtractEnsembleIts<Sacado::MP::Vector<S>, V, O>::apply(int)':
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:249:11: error: 'PseudoBlockCGSolMgr' in namespace 'Belos' does not name a type
const Belos::PseudoBlockCGSolMgr<Sc, V, O>* cg_solver =
^
/builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/packages/trilinoscouplings/examples/fenl/fenl_ensemble.hpp:251:9: error: 'cg_solver' was not declared in this scope
if (cg_solver != 0)
^
/usr/bin/cmake -E cmake_progress_report /builddir/build/BUILD/trilinos-12.8.1/Trilinos-trilinos-release-12-8-1/build/CMakeFiles
```
`RHEL7 PPC64-LittleEndian` buildroot, `GCC 4.8.5`
`cmake` configuration:
`+ /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -DCMAKE_BUILD_TYPE:STRING=Release '-DCMAKE_C_FLAGS_RELEASE:STRING=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mcpu=power8 -mtune=power8 -Wl,-z,relro -fPIC -Wl,-z,now' '-DCMAKE_CXX_FLAGS_RELEASE:STRING=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mcpu=power8 -mtune=power8 -Wl,-z,relro -fPIC -Wl,-z,now' '-DCMAKE_Fortran_FLAGS_RELEASE:STRING=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mcpu=power8 -mtune=power8 -Wl,-z,relro -fPIC -Wl,-z,now' '-DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-z,relro -fPIC -pie -Wl,-z,now -Wl,--as-needed' -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_SKIP_RPATH:BOOL=YES -DCMAKE_SKIP_INSTALL_RPATH:BOOL=YES -DBUILD_SHARED_LIBS:BOOL=ON -DTPL_ENABLE_MPI=OFF -DTrilinos_ENABLE_FORTRAN:BOOL=ON -DTrilinos_ENABLE_TESTS:BOOL=ON -DTrilinos_ENABLE_OpenMP:BOOL=ON -DTrilinos_ENABLE_PyTrilinos:BOOL=OFF -DTpetra_INST_SERIAL:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE=TRUE -DTrilinos_VERBOSE_CONFIGURE=OFF -DTrilinos_ENABLE_CXX11=ON -DTrilinos_ENABLE_MueLu:BOOL=OFF -DTPL_Boost_INCLUDE_DIRS:PATH=/usr/include/boost148 -DTPL_Boost_LIBRARIES:PATH=/usr/lib64/boost148/libboost_system.so:/usr/lib64/boost148/libboost_program_options.so:/usr/lib64/boost148/libboost_signals.so:/usr/lib64/boost148/libboost_regex.so:/usr/lib64/boost148/libboost_filesystem.so:/usr/lib64/boost148/libboost_thread.so:/usr/lib64/boost148/libboost_wserialization.so:/usr/lib64/boost148/libboost_serialization.so -DTrilinos_INSTALL_INCLUDE_DIR=/usr/include/trilinos -DTrilinos_INSTALL_LIB_DIR=/usr/lib64 -DTrilinos_INSTALL_RUNTIME_DIR=/usr/bin -DTrilinos_INSTALL_EXAMPLE_DIR=/usr/share/trilinos/examples -DTrilinos_ENABLE_STRONG_C_COMPILE_WARNINGS=OFF -DTrilinos_ENABLE_STRONG_CXX_COMPILE_WARNINGS=OFF -DTrilinos_ENABLE_EXPLICIT_INSTANTIATION:BOOL=ON -DTPL_ENABLE_gtest:BOOL=OFF -DIsorropia_ENABLE_EXAMPLES:BOOL=OFF -DTrilinos_ENABLE_STK:BOOL=OFF -DTrilinos_ENABLE_ALL_PACKAGES=ON ..`https://gitlab.osti.gov/jmwille/Trilinos/-/issues/465TrilinosCouplings scaling/example_Poisson2D_p2_tpetra.cpp failes to build in ...2016-06-27T17:48:14ZJames WillenbringTrilinosCouplings scaling/example_Poisson2D_p2_tpetra.cpp failes to build in serial*Created by: bartlettroscoe*
**Next Action Status**
The example scaling/example_Poisson2D_p2_tpetra.cpp was never intended for non-MPI builds so was marked with "COMM mpi".
**CC:** @trilinos/framework
**Description:**
I am trying ...*Created by: bartlettroscoe*
**Next Action Status**
The example scaling/example_Poisson2D_p2_tpetra.cpp was never intended for non-MPI builds so was marked with "COMM mpi".
**CC:** @trilinos/framework
**Description:**
I am trying to build all of the ST Trilinos packages in several different build configurations as part of setting up a standard SEMS Dev Env (see #158) and the TrilinosCouplings file:
examples/scaling/example_Poisson2D_p2_tpetra.cpp
does not build in a serial build of the code. When you configure and build with:
```
$ cd Trilinos/
$ mkdir BUILD/
$ cd BUILD/
$ cmake \
-DBUILD_SHARED_LIBS=ON \
-DCMAKE_BUILD_TYPE=RELEASE \
-DTrilinos_ENABLE_DEBUG=ON \
-DTrilinos_ENABLE_TESTS=ON \
-DTrilinos_ENABLE_TrilinosCouplings=ON \
..
$ make
```
you get the build failure:
```
[100%] Building CXX object packages/trilinoscouplings/examples/scaling/CMakeFiles/TrilinosCouplings_Example_Poisson2D_p2_tpetra.dir/example_Poisson2D_p2_tpetra.cpp.o
/home/rabartl/Trilinos.base/Trilinos/packages/trilinoscouplings/examples/scaling/example_Poisson2D_p2_tpetra.cpp: In function ‘int main(int, char**)’:
/home/rabartl/Trilinos.base/Trilinos/packages/trilinoscouplings/examples/scaling/example_Poisson2D_p2_tpetra.cpp:1200:46: error: ‘uCoeff’ was not declared in this scope
ArrayRCP<const scalar_type> uCoeffData = uCoeff.getData(0);
^
make[2]: *** [packages/trilinoscouplings/examples/scaling/CMakeFiles/TrilinosCouplings_Example_Poisson2D_p2_tpetra.dir/example_Poisson2D_p2_tpetra.cpp.o] Error 1
make[1]: *** [packages/trilinoscouplings/examples/scaling/CMakeFiles/TrilinosCouplings_Example_Poisson2D_p2_tpetra.dir/all] Error 2
make: *** [all] Error 2
```
Since TrilinosCouplings has not been building in a long time (see #19), I am sure that this error went unnoticed.
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 ,
[...]
```