Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2019-04-24T22:09:47Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4502Build and test failures in ATDM RDC builds on white and waterman2019-04-24T22:09:47ZJames WillenbringBuild and test failures in ATDM RDC builds on white and waterman*Created by: fryeguy52*
**CC: Trilinos Product areas leads:** @jwillenbring, @rppawlo, @kddevin, @mperego, @srajama1
**Other CC:** @bartlettroscoe @fryeguy52
## Next Action Status
Next: Waiting for PR #4761 to get tested, ap...*Created by: fryeguy52*
**CC: Trilinos Product areas leads:** @jwillenbring, @rppawlo, @kddevin, @mperego, @srajama1
**Other CC:** @bartlettroscoe @fryeguy52
## Next Action Status
Next: Waiting for PR #4761 to get tested, approved, and merged ...
## Description
As shown [here](https://testing.sandia.gov/cdash/index.php?project=Trilinos&date=&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=65&value1=Trilinos-atdm-&field2=buildname&compare2=63&value2=-rdc-&field3=buildstarttime&compare3=83&value3=2019-03-03&field4=buildstarttime&compare4=84&value4=2019-03-04), there are several failing tests and build errors in the builds:
* Trilinos-atdm-waterman-cuda-9.2-rdc-release-debug
* Trilinos-atdm-waterman-cuda-9.2-rdc-shared-release-debug
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug-pt
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-shared-release-debug
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-shared-release-debug-pt
[all test failures](https://testing.sandia.gov/cdash-dev-view/queryTests.php?project=Trilinos&filtercount=5&showfilters=1&filtercombine=and&field1=buildname&compare1=65&value1=Trilinos-atdm&field2=buildname&compare2=63&value2=-rdc-&field3=status&compare3=61&value3=Failed&field4=buildstarttime&compare4=84&value4=today&field5=buildstarttime&compare5=83&value5=yesterday)
[build error output](https://testing.sandia.gov/cdash/viewBuildError.php?buildid=4620725)
These are builds that enable cuda relocatable device code. Most of the errors look something like:
```
nvlink error : Undefined reference to '_ZN6Sacado4Impl40global_sacado_cuda_memory_pool_on_deviceE' in 'packages/intrepid2/unit-test/Discretization/Basis/HDIV_HEX_In_FEM/Serial/CMakeFiles/Intrepid2_unit-test_Discretization_Basis_HDIV_HEX_In_FEM_Serial_Test_01_SLFadDouble.dir/test_01_SLFadDouble.cpp.o'
```
or
```
nvlink warning : Stack size for entry function '_ZN6Kokkos4Impl75_GLOBAL__N__51_tmpxft_000160f8_00000000_6_Kokkos_Cuda_Task_cpp1_ii_b2872e7123cuda_task_queue_executeEPNS0_9TaskQueueINS_4CudaEEEi' cannot be statically determined
collect2: fatal error: ld terminated with signal 9 [Killed]
compilation terminated.
```
## Current Status on CDash
* [Current status of the rdc builds](https://testing.sandia.gov/cdash/index.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercount=4&showfilters=1&filtercombine=and&field1=buildname&compare1=65&value1=Trilinos-atdm-&field2=buildname&compare2=63&value2=-rdc-&field3=buildstarttime&compare3=83&value3=yesterday&field4=buildstarttime&compare4=84&value4=today) (NOTE: Click "Previous" to see the full set of builds for the previous day)
## Steps to Reproduce
One should be able to reproduce this failure on ride or white as described in:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md
More specifically, the commands given for ride or white are provided at:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md#ridewhite
For the "-pt" builds `<build-name>`:
* `Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug-pt`
* `Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-shared-release-debug-pt`
and for `<Package>` = `Kokkos`, `KokkosKernels`, `Belos`, etc., the commands to reproduce the build and test failures should be:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.s <build-name>
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_<Package>=ON \
$TRILINOS_DIR
$ ninja -j16
$ bsub -x -Is -q rhel7F -n 16 ctest -j16
```
For the other builds with `<build-name>`:
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-shared-release-debug
and for `<Package>` = `Kokkos`, `KokkosKernels`, `Belos`, etc., the commands to reproduce the build and test failures on 'white' or 'ride' should be:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.s <build-name>
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_<Package>=ON \
$TRILINOS_DIR
$ ninja -j16
$ bsub -x -Is -q rhel7F -n 16 ctest -j16
```
The build and test failures for the 'waterman' builds with `<build-name>`:
* `Trilinos-atdm-waterman-cuda-9.2-rdc-release-debug`
* `Trilinos-atdm-waterman-cuda-9.2-rdc-shared-release-debug`
one uses:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.s <build-name>
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_<Package>=ON \
$TRILINOS_DIR
$ ninja -j16
$ bsub -x -Is -n 20 ctest -j16
```
Initial cleanup of new ATDM builds of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4510Tempus: Remove Build Warnings2019-05-01T18:29:08ZJames WillenbringTempus: Remove Build Warnings*Created by: ZUUL42*
<!---
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: ZUUL42*
<!---
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/tempus
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Labels: 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.
-->
Tempus builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Tempus has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Tempus. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4623145).
## 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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4525Tpetra: Increasing number of threads leads to decrease of performance2019-05-06T22:45:30ZJames WillenbringTpetra: Increasing number of threads leads to decrease of performance*Created by: freaklovesmango*
That post refers a little to that one: #3827
I wanted to change Epetra to Tpetra, expecting a shorter execution time by increasing the number of threads while using just one MPI process, thus using share...*Created by: freaklovesmango*
That post refers a little to that one: #3827
I wanted to change Epetra to Tpetra, expecting a shorter execution time by increasing the number of threads while using just one MPI process, thus using shared memory functions via Tpetra/Kokkos.
Unfortunately, the results get worse by increasing the number of threads... and again, I wonder why.
I am using Belos with Tpetra as the underlying library on a x86-64 system.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4511Triutils: Remove Build Warnings2019-03-15T03:39:42ZJames WillenbringTriutils: Remove Build Warnings*Created by: ZUUL42*
<!---
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: ZUUL42*
<!---
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/triutils
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Labels: 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.
-->
Triutils builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Triutils has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Triutils. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4623152).
## 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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4497Tpetra: Finite Element Assembly Using Magic Routine and Local Indices2019-02-25T23:57:08ZJames WillenbringTpetra: Finite Element Assembly Using Magic Routine and Local Indices*Created by: csiefer2*
We really need a finite element assembly example which does assembly using
a) @mhoemmen 's "Magic Routine" to generate a column map and
b) local index insertion.
All FE assembly examples currently use globa...*Created by: csiefer2*
We really need a finite element assembly example which does assembly using
a) @mhoemmen 's "Magic Routine" to generate a column map and
b) local index insertion.
All FE assembly examples currently use global index insertion.
Assigning to the @trilinos/tpetra team lead for prioritizationhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4501Panzer build and test failures in ATDM RDC builds on white2019-03-04T17:04:22ZJames WillenbringPanzer build and test failures in ATDM RDC builds on white*Created by: fryeguy52*
CC: @trilinos/panzer, @mperego (Trilinos Discretizations Product Lead), @bartlettroscoe, @fryeguy52
## Next Action Status
<status-and-or-first-action>
## Description
In the build
* Trilinos-atdm-whit...*Created by: fryeguy52*
CC: @trilinos/panzer, @mperego (Trilinos Discretizations Product Lead), @bartlettroscoe, @fryeguy52
## Next Action Status
<status-and-or-first-action>
## Description
In the build
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug
* Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug-pt
several panzer tests are failing and there are several build errors on both white and ride. The failing tests can be found at this link:
[Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug](https://testing.sandia.gov/cdash/viewTest.php?onlyfailed&buildid=4621802)
[Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug-pt](https://testing.sandia.gov/cdash/viewTest.php?onlyfailed&buildid=4620711)
More information about the build errors can be found at this link:
[panzer build errors](https://testing.sandia.gov/cdash/viewBuildError.php?buildid=4620711)
These are builds that enable cuda relocatable device code
## Current Status on CDash
[Most recent builds](https://testing.sandia.gov/cdash/index.php?project=Trilinos&filtercombine=and&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=65&value1=Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug&field2=buildstarttime&compare2=84&value2=today&field3=buildstarttime&compare3=83&value3=yesterday)
## Steps to Reproduce
One should be able to reproduce this failure on ride or white as described in:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md
More specifically, the commands given for ride or white are provided at:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md#ridewhite
The exact commands to reproduce this issue should be:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh Trilinos-atdm-white-ride-cuda-9.2-gnu-7.2.0-rdc-release-debug-pt
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnvAllPtPackages.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_Panzer=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/4495Tpetra/Teuchos: Allow Teuchos Complex w/o Tpetra Complex2019-03-14T20:00:09ZJames WillenbringTpetra/Teuchos: Allow Teuchos Complex w/o Tpetra Complex*Created by: csiefer2*
This is a moral follow-on to #4080, except, I would like to reverse our decision.
I have an application that wishes to do some complex arithmetic using Teuchos::SerialDenseMatrix on the host and then later due ...*Created by: csiefer2*
This is a moral follow-on to #4080, except, I would like to reverse our decision.
I have an application that wishes to do some complex arithmetic using Teuchos::SerialDenseMatrix on the host and then later due some computing using Tpetra & CUDA.
At present, the resolution of #4080 means we have to have complex support on in both places. However, Kokkos will not compile w/ cuda if std::complex<double> is enabled.
This renders my application unable to use Trilinos on CUDA. https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4492Framework: Disable the non- dev->master PR tests in the Clean Track2019-02-25T17:28:41ZJames WillenbringFramework: Disable the non- dev->master PR tests in the Clean Track*Created by: william76*
Description
-----------
We've moved the develop -> master pull request jobs to report to the Clean track.
Since we are no longer using the old "Clean" jobs to determine the develop -> master merge, we should...*Created by: william76*
Description
-----------
We've moved the develop -> master pull request jobs to report to the Clean track.
Since we are no longer using the old "Clean" jobs to determine the develop -> master merge, we should remove them from the Clean track.
@jwillenbring I'm assuming you wanted me to remove these tests entirely since they're somewhat redundant with the PR testing for dev->master. If you would rather these be moved to the Nightly track instead, please let me know.
@trilinos/framework FYI
Task(s)
--------
- [x] Remove Linux-gcc-7.3.0-MPI_Release_gcc_7.3.0_openmpi_1.10.1_DEV
- [x] Remove Linux-gcc-4.8.4-MPI_Release_gcc_4.8.4_openmpi_1.10.1_DEV
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4486Panzer build failures in Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_s...2019-02-27T14:57:25ZJames WillenbringPanzer build failures in Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt starting 2/22/2019 taking out SPARC Trilinos Integration testing*Created by: bartlettroscoe*
CC: @trilinos/panzer , @mperego (Trilinos Discretizations Product Lead), @bartlettroscoe, @fryeguy52, @alanw0
## Next Action Status
Panzer was disabled in this build in PR #4487 on 2/24/2019 and the b...*Created by: bartlettroscoe*
CC: @trilinos/panzer , @mperego (Trilinos Discretizations Product Lead), @bartlettroscoe, @fryeguy52, @alanw0
## Next Action Status
Panzer was disabled in this build in PR #4487 on 2/24/2019 and the build 100% passed on 2/25/2019. PR #4503 that re-enables Panzer in this build was merged on 2/26/2019. Panzer built and passed tests in clang-5.0.1 build on 2/27/2019 as shown [here](https://testing.sandia.gov/cdash-dev-view/index.php?project=Trilinos&parentid=4628934).
## Description
As shown in [this query](https://testing.sandia.gov/cdash-dev-view/index.php?project=Trilinos&date=2019-02-23&filtercount=3&showfilters=1&filtercombine=and&field1=subprojects&compare1=93&value1=Panzer&field2=buildname&compare2=61&value2=Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt&field3=buildstarttime&compare3=83&value3=2019-02-18) starting 2/22/2018 Panzer has many build and install failures in the build
* Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt
The build failures, for example, are shown [here](https://testing.sandia.gov/cdash-dev-view/viewBuildError.php?buildid=4612306) and show STK link failures like:
```
data<(stk::topology::topology_t)0, void>::spatial_dimension_vector
>>> referenced by /scratch/rabartl/Trilinos.base/NightlyBuilds/Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt/SRC_AND_BUILD/Trilinos/packages/stk/stk_mesh/stk_mesh/base/MetaData.cpp
>>> MetaData.cpp.o:(stk::topology::apply_functor<stk::topology_detail::defined_on_spatial_dimension_impl>::operator()(stk::topology::topology_t)) in archive packages/stk/stk_mesh/stk_mesh/base/libstk_mesh_base.a
/usr/netpub/lld/bin/ld: error: symbol 'stk::topology_detail::topology_data<(stk::topology::topology_t)0, void>::spatial_dimension_vector' defined in packages/stk/stk_mesh/stk_mesh/base/libstk_mesh_base.a(MetaData.cpp.o) has no type
/usr/netpub/lld/bin/ld: error: undefined symbol: stk::topology_detail::topology_data<(stk::topology::topology_t)1, void>::spatial_dimension_vector
>>> referenced by /scratch/rabartl/Trilinos.base/NightlyBuilds/Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt/SRC_AND_BUILD/Trilinos/packages/stk/stk_mesh/stk_mesh/base/MetaData.cpp
>>> MetaData.cpp.o:(stk::topology::apply_functor<stk::topology_detail::defined_on_spatial_dimension_impl>::operator()(stk::topology::topology_t)) in archive packages/stk/stk_mesh/stk_mesh/base/libstk_mesh_base.a
```
The new commits pulled on 2/22/2019 in this build are shown [here](https://testing.sandia.gov/cdash-dev-view/viewNotes.php?buildid=4607144#!#note0) and it seems likely the STK update in the commits shown below from @alanw0 are the likely cause.
<details>
<summary><b>STK Commits (click to expand)</b></summary>
```
400560bc40: Make stk_ngp_test usable as header-only. (Try to avoid the need for --rdc in cuda build.)
Author: Alan Williams <william@sandia.gov>
Date: Tue Feb 19 15:35:08 2019 -0700
M packages/stk/stk_ngp_test/stk_ngp_test/CMakeLists.txt
M packages/stk/stk_ngp_test/stk_ngp_test/GlobalReporter.cpp
M packages/stk/stk_ngp_test/stk_ngp_test/GlobalReporter.hpp
M packages/stk/stk_ngp_test/stk_ngp_test/Reporter.cpp
M packages/stk/stk_ngp_test/stk_ngp_test/Reporter.hpp
M packages/stk/stk_ngp_test/stk_ngp_test/ngp_test.cpp
M packages/stk/stk_ngp_test/stk_ngp_test/ngp_test.hpp
b92e9d8bfe: Try to solve the undefined extern function for cuda in stk_ngp_test.
Author: Alan Williams <william@sandia.gov>
Date: Thu Feb 14 15:08:57 2019 -0700
M packages/stk/stk_ngp_test/stk_ngp_test/Reporter.cpp
M packages/stk/stk_ngp_test/stk_ngp_test/Reporter.hpp
6d16a65a94: Fix compile error in stk_ngp_test file.
Author: Alan Williams <william@sandia.gov>
Date: Wed Feb 13 11:50:20 2019 -0700
M packages/stk/stk_ngp_test/stk_ngp_test/Reporter.hpp
dbf8d78fca: Another tweak to deprecating ngp::Field::copy_* to become private.
Author: Alan Williams <william@sandia.gov>
Date: Tue Feb 12 12:20:01 2019 -0700
M packages/stk/stk_ngp/stk_ngp/NgpField.hpp
1ea65f4ffc: Ok, one more try.
Author: Alan Williams <william@sandia.gov>
Date: Tue Feb 12 12:05:08 2019 -0700
A packages/stk/stk_unit_tests/stk_ngp_test/CMakeLists.txt
7557aafa7f: Fix the macro managing the deprecation of ngp::Field's copy_* methods from public to private.
Author: Alan Williams <william@sandia.gov>
Date: Mon Feb 11 13:26:26 2019 -0700
M packages/stk/stk_ngp/stk_ngp/NgpField.hpp
62a1e8bb44: Fix stk cmake files.
Author: Alan Williams <william@sandia.gov>
Date: Mon Feb 11 08:28:40 2019 -0700
M cmake/dependencies/TrilinosPackageDependencies.xml
M packages/stk/cmake/Dependencies.cmake
M packages/stk/stk_balance/stk_balance/balance.cpp
M packages/stk/stk_balance/stk_balance/balanceUtils.cpp
M packages/stk/stk_balance/stk_balance/balanceUtils.hpp
A packages/stk/stk_balance/unit_tests/UnitTestColoring.cpp
M packages/stk/stk_doc_tests/stk_io/howToWriteMesh.cpp
M packages/stk/stk_mesh/stk_mesh/base/BulkData.cpp
M packages/stk/stk_mesh/stk_mesh/base/Part.hpp
M packages/stk/stk_mesh/stk_mesh/base/Relation.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/FieldBaseImpl.cpp
M packages/stk/stk_ngp/cmake/Dependencies.cmake
M packages/stk/stk_ngp_test/cmake/Dependencies.cmake
A packages/stk/stk_ngp_test/stk_ngp_test/CMakeLists.txt
M packages/stk/stk_search/stk_search/KDTree_impl.hpp
M packages/stk/stk_unit_test_utils/CMakeLists.txt
M packages/stk/stk_unit_test_utils/cmake/Dependencies.cmake
M packages/stk/stk_unit_tests/cmake/Dependencies.cmake
M packages/stk/stk_util/stk_util/util/SortAndUnique.hpp
a6c29b6b13: Added new stk subpackage stk_ngp_test to TrilinosPackageDependencies.xml
Author: Alan Williams <william@sandia.gov>
Date: Fri Feb 8 16:37:12 2019 -0700
M cmake/dependencies/TrilinosPackageDependencies.xml
006dfdce93: Bring recent stk development into Trilinos.
Author: Alan Williams <william@sandia.gov>
Date: Thu Feb 7 10:30:23 2019 -0700
M packages/stk/stk_balance/Jamfile
M packages/stk/stk_balance/integration_tests/StkbalanceUserSupport.cpp
M packages/stk/stk_balance/stk_balance/internal/StkBalanceUtils.cpp
M packages/stk/stk_doc_tests/stk_io/howToWriteMesh.cpp
M packages/stk/stk_doc_tests/stk_io/writeResults.cpp
M packages/stk/stk_exp/unit_tests/kokkos/copy_kokkos_memory.cpp
M packages/stk/stk_exp/unit_tests/kokkos/create_kokkos_view.cpp
M packages/stk/stk_exp/unit_tests/kokkos/saxpy_kokkos.cpp
M packages/stk/stk_exp/unit_tests/kokkos/saxpy_kokkos.hpp
M packages/stk/stk_exp/unit_tests/kokkos/unit_test_kokkos.cpp
M packages/stk/stk_exp/unit_tests/kokkos/unit_test_kokkos_saxpy.cpp
M packages/stk/stk_expreval/Jamfile
M packages/stk/stk_expreval/stk_expreval/Evaluator.cpp
M packages/stk/stk_integration_tests/stk_mesh/IntegrationTestElementBlockMembership.cpp
M packages/stk/stk_io/Jamfile
M packages/stk/stk_io/stk_io/FieldAndName.hpp
M packages/stk/stk_io/stk_io/IossBridge.cpp
M packages/stk/stk_io/stk_io/IossBridge.hpp
M packages/stk/stk_io/stk_io/OutputFile.cpp
M packages/stk/stk_io/stk_io/ProcessSetsOrBlocks.hpp
M packages/stk/stk_io/stk_io/StkIoUtils.cpp
M packages/stk/stk_io/stk_io/StkIoUtils.hpp
M packages/stk/stk_learning/Kokkos/KokkosFieldBLAS.C
M packages/stk/stk_learning/Kokkos/KokkosTutorial04.C
M packages/stk/stk_learning/Kokkos/KokkosViewAllocOnDevice.C
M packages/stk/stk_learning/Kokkos/KokkosWithTopology.C
M packages/stk/stk_learning/Kokkos/Kokkos_TeamReductionTest.C
M packages/stk/stk_learning/Kokkos/mtk_kokkos.h
M packages/stk/stk_learning/Kokkos/testKokkosEncapsulation.C
M packages/stk/stk_mesh/Jamfile
M packages/stk/stk_mesh/stk_mesh/base/BulkData.cpp
M packages/stk/stk_mesh/stk_mesh/base/BulkData.hpp
M packages/stk/stk_mesh/stk_mesh/base/CoordinateSystems.cpp
M packages/stk/stk_mesh/stk_mesh/base/CoordinateSystems.hpp
M packages/stk/stk_mesh/stk_mesh/base/CreateEdges.cpp
M packages/stk/stk_mesh/stk_mesh/base/EntityKey.hpp
M packages/stk/stk_mesh/stk_mesh/base/FEMHelpers.cpp
M packages/stk/stk_mesh/stk_mesh/base/FieldBase.hpp
M packages/stk/stk_mesh/stk_mesh/base/FieldParallel.cpp
M packages/stk/stk_mesh/stk_mesh/base/MetaData.cpp
M packages/stk/stk_mesh/stk_mesh/base/MetaData.hpp
M packages/stk/stk_mesh/stk_mesh/base/Part.hpp
M packages/stk/stk_mesh/stk_mesh/base/Relation.cpp
M packages/stk/stk_mesh/stk_mesh/base/Relation.hpp
M packages/stk/stk_mesh/stk_mesh/base/Selector.cpp
M packages/stk/stk_mesh/stk_mesh/base/Selector.hpp
M packages/stk/stk_mesh/stk_mesh/base/SkinBoundary.cpp
M packages/stk/stk_mesh/stk_mesh/base/SkinBoundary.hpp
M packages/stk/stk_mesh/stk_mesh/base/SkinMeshUtil.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/BucketRepository.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/BucketRepository.hpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/EquivalentEntityBlocks.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/EquivalentEntityBlocks.hpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/FieldBaseImpl.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/FieldRepository.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/MeshImplUtils.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/PartImpl.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/PartImpl.hpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/Partition.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/ElemElemGraph.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/ElemElemGraphImpl.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/ElemElemGraphImpl.hpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/ElemGraphShellConnections.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/GraphEdgeData.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/GraphEdgeData.hpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/ParallelInfoForGraph.cpp
M packages/stk/stk_mesh/stk_mesh/baseImpl/elementGraph/SparseGraph.hpp
M packages/stk/stk_ngp/Jamfile
M packages/stk/stk_ngp/stk_ngp/Ngp.hpp
M packages/stk/stk_ngp/stk_ngp/NgpAtomics.hpp
M packages/stk/stk_ngp/stk_ngp/NgpDynamicMesh.hpp
M packages/stk/stk_ngp/stk_ngp/NgpField.hpp
M packages/stk/stk_ngp/stk_ngp/NgpFieldManager.hpp
M packages/stk/stk_ngp/stk_ngp/NgpMesh.hpp
M packages/stk/stk_ngp/stk_ngp/NgpMultistateField.hpp
M packages/stk/stk_ngp/stk_ngp/NgpReductions.hpp
M packages/stk/stk_ngp/stk_ngp/NgpSpaces.hpp
A packages/stk/stk_ngp_test/CMakeLists.txt
C070 packages/stk/stk_ngp/Jamfile packages/stk/stk_ngp_test/Jamfile
A packages/stk/stk_ngp_test/cmake/Dependencies.cmake
A packages/stk/stk_ngp_test/stk_ngp_test/GlobalReporter.cpp
A packages/stk/stk_ngp_test/stk_ngp_test/GlobalReporter.hpp
A packages/stk/stk_ngp_test/stk_ngp_test/NgpTestDeviceMacros.hpp
A packages/stk/stk_ngp_test/stk_ngp_test/Reporter.cpp
A packages/stk/stk_ngp_test/stk_ngp_test/Reporter.hpp
A packages/stk/stk_ngp_test/stk_ngp_test/main/main.cpp
A packages/stk/stk_ngp_test/stk_ngp_test/ngp_test.cpp
A packages/stk/stk_ngp_test/stk_ngp_test/ngp_test.hpp
M packages/stk/stk_performance_tests/stk_mesh/CommunicateFieldData.cpp
M packages/stk/stk_search/Jamfile
M packages/stk/stk_search_util/Jamfile
M packages/stk/stk_simd/stk_simd/Simd.hpp
M packages/stk/stk_simd/stk_simd/avx/Avx.hpp
M packages/stk/stk_simd/stk_simd/avx512/Avx512.hpp
M packages/stk/stk_simd/stk_simd/no_simd/NoSimd.hpp
M packages/stk/stk_simd/stk_simd/sse/Sse.hpp
M packages/stk/stk_simd/stk_simd_view/simd_index.hpp
M packages/stk/stk_simd/stk_simd_view/simd_parallel.hpp
M packages/stk/stk_simd/stk_simd_view/simd_view.hpp
M packages/stk/stk_simd/unit_tests/UnitTestStkSimdMathDouble.cpp
M packages/stk/stk_simd/unit_tests/UnitTestStkSimdView.cpp
M packages/stk/stk_simd/unit_tests/UnitTestStkSimdView2d.cpp
M packages/stk/stk_simd/unit_tests/UnitTestStkSimdView3d.cpp
M packages/stk/stk_tools/Jamfile
A packages/stk/stk_tools/stk_tools/mesh_tools/FixNodeSharingViaSearch.cpp
A packages/stk/stk_tools/stk_tools/mesh_tools/FixNodeSharingViaSearch.hpp
M packages/stk/stk_topology/Jamfile
M packages/stk/stk_topology/stk_topology/topology_detail/meta_functions.hpp
A packages/stk/stk_topology/stk_topology/topology_detail/topology_data.cpp
M packages/stk/stk_topology/stk_topology/topology_detail/topology_data.hpp
M packages/stk/stk_topology/stk_topology/topology_type.hpp
M packages/stk/stk_transfer/Jamfile
M packages/stk/stk_unit_test_utils/FaceTestingUtils.cpp
M packages/stk/stk_unit_test_utils/Jamfile
M packages/stk/stk_unit_test_utils/MeshFileFixture.hpp
M packages/stk/stk_unit_test_utils/MeshFixture.hpp
M packages/stk/stk_unit_test_utils/unit_main_lib/UnitTestMain.cpp
M packages/stk/stk_unit_tests/CMakeLists.txt
M packages/stk/stk_unit_tests/cmake/Dependencies.cmake
M packages/stk/stk_unit_tests/stk_mesh/UnitTestBucketRepository.cpp
M packages/stk/stk_unit_tests/stk_mesh/UnitTestField.cpp
M packages/stk/stk_unit_tests/stk_mesh/UnitTestFieldImpl.cpp
M packages/stk/stk_unit_tests/stk_mesh/UnitTestModificationEnd.hpp
M packages/stk/stk_unit_tests/stk_mesh/UnitTestPartitions.cpp
M packages/stk/stk_unit_tests/stk_mesh/face_creation/element_graph/BulkDataElementGraphTester.hpp
M packages/stk/stk_unit_tests/stk_ngp/KokkosBulkDataBucketCentroidCalculation.cpp
M packages/stk/stk_unit_tests/stk_ngp/KokkosCentroidCalculation.cpp
M packages/stk/stk_unit_tests/stk_ngp/KokkosCentroidCalculation.hpp
M packages/stk/stk_unit_tests/stk_ngp/KokkosNodalVolume.cpp
M packages/stk/stk_unit_tests/stk_ngp/NgpFieldPerformanceTest.cpp
M packages/stk/stk_unit_tests/stk_ngp/NpgMultistateFieldTest.cpp
M packages/stk/stk_unit_tests/stk_ngp/howToNgp.cpp
A packages/stk/stk_unit_tests/stk_ngp/ngpFieldTest.cpp
A packages/stk/stk_unit_tests/stk_ngp_test/utest_KokkosConfigInfo.cpp
A packages/stk/stk_unit_tests/stk_ngp_test/utest_NgpTestAPI.cpp
A packages/stk/stk_unit_tests/stk_ngp_test/utest_NgpTestMacros.cpp
A packages/stk/stk_unit_tests/stk_ngp_test/utest_Reporter.cpp
M packages/stk/stk_unit_tests/stk_tools/createMesh.cpp
M packages/stk/stk_unit_tests/stk_topology/unit_test_hex.cpp
M packages/stk/stk_unit_tests/stk_topology/unit_test_validate_topology_data.cpp
M packages/stk/stk_unit_tests/stk_util/environment/UnitTestThrowMacros.cpp
M packages/stk/stk_usecases/mesh/MeshUseCase_3.cpp
M packages/stk/stk_usecases/mesh/UseCase_ChangeOwner.cpp
M packages/stk/stk_util/Jamfile
M packages/stk/stk_util/stk_util/diag/Option.cpp
M packages/stk/stk_util/stk_util/diag/Option.hpp
R099 packages/stk/stk_util/stk_util/util/Resource2.cpp packages/stk/stk_util/stk_util/diag/Resource2.cpp
R100 packages/stk/stk_util/stk_util/util/Resource2.h packages/stk/stk_util/stk_util/diag/Resource2.h
M packages/stk/stk_util/stk_util/diag/WriterParser.cpp
M packages/stk/stk_util/stk_util/parallel/CommBufferV.hpp
M packages/stk/stk_util/stk_util/parallel/CommNeighbors.cpp
M packages/stk/stk_util/stk_util/parallel/mpi_filebuf.cpp
M packages/stk/stk_util/stk_util/util/StkNgpVector.hpp
```
</details>
## Current Status on CDash
The status of the Panzer build in this clang-5.0.1 build over the last few days can be see in [this query](https://testing.sandia.gov/cdash-dev-view/index.php?project=Trilinos&date=2019-02-23&filtercount=3&showfilters=1&filtercombine=and&field1=subprojects&compare1=93&value1=Panzer&field2=buildname&compare2=61&value2=Trilinos-atdm-cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt&field3=buildstarttime&compare3=83&value3=4%20days%20ago).
## Steps to Reproduce
One should be able to reproduce this failure on any CEE RHEL6 machine as described in:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md
More specifically, the commands given for the system <supported-atdm-system> are provided at:
* https://github.com/trilinos/Trilinos/blob/develop/cmake/std/atdm/README.md#cee-rhel6-environment
The exact commands to reproduce the build failures should be:
```
$ cd <some_build_dir>/
$ source $TRILINOS_DIR/cmake/std/atdm/load-env.sh \
cee-rhel6_clang-5.0.1_openmpi-1.10.2_serial_static_opt
$ cmake \
-GNinja \
-DTrilinos_CONFIGURE_OPTIONS_FILE:STRING=cmake/std/atdm/ATDMDevEnv.cmake \
-DTrilinos_ENABLE_TESTS=ON -DTrilinos_ENABLE_Panzer=ON \
$TRILINOS_DIR
$ ninja -j16
```
Keep promoted "ATDM" builds of Trilinos cleanhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4477Piro: Remove build warnings2019-02-26T00:24:23ZJames WillenbringPiro: Remove build warnings*Created by: ZUUL42*
<!---
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: ".
-->
<!---
Replace <team...*Created by: ZUUL42*
<!---
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: ".
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/piro
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Labels: 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.
-->
Piro builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Piro has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Piro. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4589558).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4476Ifpack2: Remove build warnings2019-02-26T00:24:19ZJames WillenbringIfpack2: Remove build warnings*Created by: ZUUL42*
<!---
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: ".
-->
<!---
Replace <team...*Created by: ZUUL42*
<!---
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: ".
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/ifpack2
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Labels: 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.
-->
Ifpack2 builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Ifpack2 has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Ifpack2. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4590377).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4475Anasazi: Remove build warnings2019-03-15T03:39:44ZJames WillenbringAnasazi: Remove build warnings*Created by: ZUUL42*
<!---
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: ZUUL42*
<!---
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/anasazi
<!---
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.
-->
Anasazi builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Anasazi has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Anasazi. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4595716).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4474Intrepid2: Remove build warnings2019-02-26T00:24:21ZJames WillenbringIntrepid2: Remove build warnings*Created by: ZUUL42*
<!---
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: ZUUL42*
<!---
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/intrepid2
<!---
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.
-->
Intrepid2 builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Intrepid2 has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Intrepid2. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4595675).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4470stk broke Albany builds2019-02-25T20:19:21ZJames Willenbringstk broke Albany builds*Created by: ikalash*
Another day, another issue on Trilinos breaking the Albany build...
Here is what we see in our nightlies:
```
[ 66%] Building CXX object packages/stk/stk_unit_test_utils/CMakeFiles/stk_unit_test_utils.dir/Read...*Created by: ikalash*
Another day, another issue on Trilinos breaking the Albany build...
Here is what we see in our nightlies:
```
[ 66%] Building CXX object packages/stk/stk_unit_test_utils/CMakeFiles/stk_unit_test_utils.dir/ReadWriteSidesetTester.cpp.o
/.../repos/Trilinos/SCOREC/stk/apfSTK.cc: In function 'T* apf::makeStkField(const char*, apf::StkMetaData*) [with T = stk::mesh::Field; apf::StkMetaData = stk::mesh::MetaData]':
```
We are getting the following error:
```
[ 66%] Building CXX object SCOREC/stk/CMakeFiles/apf_stk.dir/apfMeshSTK.cc.o
[ 66%] Building CXX object packages/stk/stk_unit_test_utils/CMakeFiles/stk_unit_test_utils.dir/ParallelGtestOutput.cpp.o
[ 66%] Building CXX object packages/stk/stk_unit_test_utils/CMakeFiles/stk_unit_test_utils.dir/ParticleUtils.cpp.o
[ 66%] Building CXX object SCOREC/stk/CMakeFiles/apf_stk.dir/apfSTK.cc.o
[ 66%] Building CXX object SCOREC/stk/CMakeFiles/apf_stk.dir/apfExodusOutput.cc.o
[ 66%] Building CXX object packages/stk/stk_tools/stk_tools/CMakeFiles/stk_tools_lib.dir/mesh_clone/MeshCloneIo.cpp.o [ 66%] Building CXX object packages/tpetra/core/src/CMakeFiles/tpetra.dir/Tpetra_computeRowAndColumnOneNorms_DOUBLE_INT_LONG_LONG_SERIAL.cpp.o
[ 66%] Building CXX object packages/tpetra/core/src/CMakeFiles/tpetra.dir/Tpetra_replaceDiagonalCrsMatrix_LONG_LONG_INT_LONG_LONG_SERIAL.cpp.o
[ 66%] Building CXX object packages/stk/stk_unit_test_utils/CMakeFiles/stk_unit_test_utils.dir/ReadWriteSidesetTester.cpp.o /.../repos/Trilinos/SCOREC/stk/apfSTK.cc: In function 'T* apf::makeStkField(const char*, apf::StkMetaData*) [with T = stk::mesh::Field; apf::StkMetaData = stk::mesh::MetaData]': repos/Trilinos/SCOREC/stk/apfSTK.cc:130:14: error: 'put_field' is not a member of 'stk::mesh'
repos/Trilinos/SCOREC/stk/apfSTK.cc:130:14: error: 'put_field' is not a member of 'stk::mesh'
```
http://cdash.sandia.gov/CDash-2-3-0/viewBuildError.php?buildid=81771
Did the put_field method go away in STK? If so, is there an alternate routine we should be doing?
@trilinos/stk
k https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4473Belos: Remove build warnings2019-03-28T21:20:40ZJames WillenbringBelos: Remove build warnings*Created by: ZUUL42*
<!---
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: ZUUL42*
<!---
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/belos
<!---
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.
-->
Belos builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Belos has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Belos. The CDash report can be found [here](https://testing.sandia.gov/cdash/viewBuildError.php?buildid=4589921).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4468Epetra: Remove build warnings2019-03-15T03:39:45ZJames WillenbringEpetra: Remove build warnings*Created by: ZUUL42*
<!---
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: ".
-->
<!---
Replace <team...*Created by: ZUUL42*
<!---
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: ".
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/epetra
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Labels: 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.
-->
Epetra builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently Epetra has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for Epetra. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4584123).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4469ROL: Remove build warnings2019-03-15T03:39:47ZJames WillenbringROL: Remove build warnings*Created by: ZUUL42*
<!---
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: ZUUL42*
<!---
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/rol
<!---
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.
-->
ROL builds should not emit any warnings that will be promoted to errors once Werror is set in the GCC 7.2.0 automated build.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
Currently ROL has a number of warnings that need to be handled before we can set Werror for all packages.
A recent test build was performed with -Werror set for ROL. The CDash report can be found [here](https://testing-vm.sandia.gov/cdash/viewBuildError.php?buildid=4595635).
## Motivation, Context and Related Issues
<!---
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.
-->
Issue #3178 is working toward turning Warnings as Errors on for all packages.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4464MueLu: add unit tests for class Zoltan2Interface2019-02-21T21:29:02ZJames WillenbringMueLu: add unit tests for class Zoltan2Interface*Created by: jhux2*
While looking at another issue, I discovered there are no MueLu unit tests for the Zoltan2Interface class. This should be fixed.
@trilinos/muelu *Created by: jhux2*
While looking at another issue, I discovered there are no MueLu unit tests for the Zoltan2Interface class. This should be fixed.
@trilinos/muelu https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4457Building Sacado with relocatable device code enabled2019-03-05T14:56:53ZJames WillenbringBuilding Sacado with relocatable device code enabled*Created by: jwillenbring*
<!---
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 th...*Created by: jwillenbring*
<!---
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/sacado
CC: @trilinos/framework @bartlettroscoe @rppawlo @alanw0
<!---
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.
-->
Multiple major Trilinos customers now need to build Trilinos with relocatable device code enabled for CUDA builds. Per @rppawlo this can take a lot of effort to get working.
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
I fired off a build with rdc enabled to help gauge our current status and encountered [these issues](https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&parentid=4589862) with Sacado (note that the system caps errors at 50).
## 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.
-->
I had two objectives in filing this ticket.
1. Post the current Sacado issues I am seeing so that they can be evaluated and possibly fixed.
1. Start a broader discussion about the effort that might be required to get rdc working across Trilinos.
## 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.
-->
I used the jwillenbring/trilinos rdc_test branch and the standard PR CUDA build on ride to produce the errors. A fix can be tested by submitting a PR, or I would be willing to test a branch that someone points me to.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4461Framework: Autotester Occasionally Refuses to Do Inspection2019-03-08T17:10:35ZJames WillenbringFramework: Autotester Occasionally Refuses to Do Inspection*Created by: csiefer2*
Which means you can't merge a tested, approved PR.
This can be 'fixed' by throwing on 'AT: RETEST' and burning another 4 hours of testing time (if the test machines all work), but this is getting annoying.
@...*Created by: csiefer2*
Which means you can't merge a tested, approved PR.
This can be 'fixed' by throwing on 'AT: RETEST' and burning another 4 hours of testing time (if the test machines all work), but this is getting annoying.
@trilinos/framework @william76 @jwillenbring