Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2017-06-21T14:59:49Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1421Getting spammed by configure failures for Linux-GCC-4.7.2-RELEASE_DEV_MueLu_M...2017-06-21T14:59:49ZJames WillenbringGetting spammed by configure failures for Linux-GCC-4.7.2-RELEASE_DEV_MueLu_Matlab Nightly build*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/muelu, @maherou
**Description**
I am getting spammed by 4 CDash emails every day for configure failures for the "Nightly" build `Linux-GCC-4.7.2-RELEASE_DEV_Mue...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/muelu, @maherou
**Description**
I am getting spammed by 4 CDash emails every day for configure failures for the "Nightly" build `Linux-GCC-4.7.2-RELEASE_DEV_MueLu_Matlab`. The most recent is:
* https://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=2946611
This fails with:
```
Processing enabled TPL: MATLAB (enabled explicitly, disable with -DTPL_ENABLE_MATLAB=OFF)
-- MATLAB_LIBRARY_NAMES='mex;mx;eng'
-- Searching for libs in MATLAB_LIBRARY_DIRS='/nfsshare/matlab/bin/glnxa64'
-- Searching for a lib in the set "mex":
-- Searching for lib 'mex' ...
-- NOTE: Did not find a lib in the lib set "mex" for the TPL 'MATLAB'!
-- ERROR: Could not find the libraries for the TPL 'MATLAB'!
-- TIP: If the TPL 'MATLAB' is on your system then you can set:
-DMATLAB_LIBRARY_DIRS='<dir0>;<dir1>;...'
to point to the directories where these libraries may be found.
Or, just set:
-DTPL_MATLAB_LIBRARIES='<path-to-libs0>;<path-to-libs1>;...'
to point to the full paths for the libraries which will
bypass any search for libraries and these libraries will be used without
question in the build. (But this will result in a build-time error
if not all of the necessary symbols are found.)
-- ERROR: Failed finding all of the parts of TPL 'MATLAB' (see above), Aborting!
CMake Error at cmake/TPLs/FindTPLMATLAB.cmake:94 (MESSAGE):
Could not find mex.
Call Stack (most recent call first):
/home/nightlyTesting/Trilinos/cmake/tribits/core/package_arch/TribitsProcessEnabledTpl.cmake:89 (INCLUDE)
/home/nightlyTesting/Trilinos/cmake/tribits/core/package_arch/TribitsGlobalMacros.cmake:1647 (TRIBITS_PROCESS_ENABLED_TPL)
/home/nightlyTesting/Trilinos/cmake/tribits/core/package_arch/TribitsProjectImpl.cmake:202 (TRIBITS_PROCESS_ENABLED_TPLS)
/home/nightlyTesting/Trilinos/cmake/tribits/core/package_arch/TribitsProject.cmake:93 (TRIBITS_PROJECT_IMPL)
CMakeLists.txt:93 (TRIBITS_PROJECT)
```
This thing is a "Matlab" build. If that does not qualify for the "Specialized" track, I don't know what does.
Can we please either fix this or demote this to "Specialized" or "Experimental"? Letting this fail day after day is only going to teach people to filter and ignore CDash emails.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1410yaml-cpp SEMS module built using GCC 4.4.7 (could break C++11)2017-09-02T15:43:58ZJames Willenbringyaml-cpp SEMS module built using GCC 4.4.7 (could break C++11)*Created by: mhoemmen*
@trilinos/framework *Created by: mhoemmen*
@trilinos/framework https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1412Question on how to build Kokkos with Tpetra2017-06-21T19:37:59ZJames WillenbringQuestion on how to build Kokkos with Tpetra*Created by: kvmkrao*
**CC: @wfspotz**
I set Trilonos path and compiled a simple Kokkos with Tpetra code (https://github.com/trilinos/Trilinos_tutorial/wiki/KokkosExample01) with CMakeList.txt. The compilation was not successful beca...*Created by: kvmkrao*
**CC: @wfspotz**
I set Trilonos path and compiled a simple Kokkos with Tpetra code (https://github.com/trilinos/Trilinos_tutorial/wiki/KokkosExample01) with CMakeList.txt. The compilation was not successful because of the following errors:
_Scanning dependencies of target example
[ 50%] Building CXX object CMakeFiles/example.dir/kokkosexample01.cpp.o
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Error.hpp(76): error: namespace "Kokkos::Impl" has no member "cuda_abort"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Increment.hpp(61): error: namespace "Kokkos" has no member "atomic_fetch_add"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Increment.hpp(76): error: namespace "Kokkos" has no member "atomic_fetch_add"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Increment.hpp(91): error: namespace "Kokkos" has no member "atomic_fetch_add"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Increment.hpp(106): error: namespace "Kokkos" has no member "atomic_fetch_add"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Decrement.hpp(63): error: namespace "Kokkos" has no member "atomic_fetch_sub"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Decrement.hpp(78): error: namespace "Kokkos" has no member "atomic_fetch_sub"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Decrement.hpp(93): error: namespace "Kokkos" has no member "atomic_fetch_sub"
/oasis/scratch/comet/vkotteda/Software/trilinos/install/include/impl/Kokkos_Atomic_Decrement.hpp(108): error: namespace "Kokkos" has no member "atomic_fetch_sub"
9 errors detected in the compilation of "/tmp/tmpxft_00001cb6_00000000-7_kokkosexample01.cpp1.ii".
make[2]: *** [CMakeFiles/example.dir/kokkosexample01.cpp.o] Error 2
make[1]: *** [CMakeFiles/example.dir/all] Error 2
make: *** [all] Error 2
_
I thought that these errors are not related to the installation of Trilinos and created a file using Makefile.export.Trilinos (please see the attachment, #1409 ) to compile the cpp code as there is no documentation to compile Kokkos (CUDA) with Tpetra codes.
I use CMakeList.txt to compile MPI/E(T)petra codes and Makefile to compile the Kokkos codes.
Can I use the attachment to compile those codes ?
[compile.txt](https://github.com/trilinos/Trilinos/files/1065170/compile.txt)https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1407Trilinos CDash site testing.sandia.gov/cdash/ broken starting 6/7/2017?2017-06-23T13:12:09ZJames WillenbringTrilinos CDash site testing.sandia.gov/cdash/ broken starting 6/7/2017?*Created by: bartlettroscoe*
**CC:** @trilinos/framework
**Description:**
The Trilinos CDash site appears to be badly broken and not accepting any new data (and has other problems as well). That is super bad.
----
From: tr...*Created by: bartlettroscoe*
**CC:** @trilinos/framework
**Description:**
The Trilinos CDash site appears to be badly broken and not accepting any new data (and has other problems as well). That is super bad.
----
From: trilinos-framework-bounces@software.sandia.gov [mailto:trilinos-framework-bounces@software.sandia.gov] On Behalf Of Bartlett, Roscoe A
Sent: Wednesday, June 07, 2017 9:47 PM
To: Trilinos Developers List <trilinos-developers@trilinos.org>
Cc: trilinos-framework@software.sandia.gov
Subject: [Trilinos-Framework] FW: Problems with testing.sandia.gov/cdash/?
Trilinos Developers,
FYI:
The Trilinos CDash site appears to be majorly broken as of earlier this morning. Please be super careful in pushing to Trilinos until this can be fixed.
One suggestion is to use checkin-test-sems.sh to push as per:
* https://github.com/trilinos/Trilinos/wiki/Policies-%7C-Safe-Checkin-Testing
At least that way, we can be assured that at least the CI build will keep working.
-Ross
From: Bartlett, Roscoe A
Sent: Wednesday, June 07, 2017 9:45 PM
To: Zack Galbreath <zack.galbreath@kitware.com>
Cc: trilinos-framework@software.sandia.gov
Subject: Problems with testing.sandia.gov/cdash/?
Hello Zack,
If you can find some time, can you please take a look at the current Trilinos CDash site:
* https://testing.sandia.gov/cdash/
?
Some things seem very broken on it.
For one, it stopped accepting data for the CI build shown at:
* https://testing.sandia.gov//cdash/index.php?project=Trilinos&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Linux-GCC-4.9.3-MPI_RELEASE_DEBUG_SHARED_PT_CI&field2=groupname&compare2=61&value2=Continuous&field3=buildstarttime&compare3=84&value3=now
Second, the “feed” at:
* https://testing.sandia.gov//cdash/index.php?project=Trilinos&display=project
says that no files have changed in 201 days.
Third, the build links on the site:
* https://testing.sandia.gov//cdash/index.php?project=Trilinos&filtercount=3&showfilters=1&filtercombine=and&field1=buildname&compare1=61&value1=Linux-GCC-4.9.3-MPI_RELEASE_DEBUG_SHARED_PT_CI&field2=groupname&compare2=61&value2=Continuous&field3=buildstarttime&compare3=84&value3=now
are broken. For example, if you click the build name Linux-GCC-4.9.3-MPI_RELEASE_DEBUG_SHARED_PT_CI at the top, it takes you to:
* https://cdash/index.php?project=Trilinos&parentid=2938928&filtercount=3&showfilters=1&field1=groupname&compare1=61&value1=Continuous&field2=buildstarttime&compare2=84&value2=now&filtercombine=and
See, it is missing the “testing.sandia.gov” part.
Did CDash get upgraded by accident somehow to some very broken version of CDash?
-Ross
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1404Framework: reduce size of MPI_RELEASE_DEBUG_SHARED_PT build2017-06-07T16:34:45ZJames WillenbringFramework: reduce size of MPI_RELEASE_DEBUG_SHARED_PT build*Created by: ibaned*
So, I tried to do a `checkin-test-sems` run for #1396 and ran out of space on CEE.
The build directory is 70 GB (at the point it ran out of memory), and my entire home directory quota is 100 GB.
Looking around...*Created by: ibaned*
So, I tried to do a `checkin-test-sems` run for #1396 and ran out of space on CEE.
The build directory is 70 GB (at the point it ran out of memory), and my entire home directory quota is 100 GB.
Looking around, it seems like a lot of space could be saved by not building examples. Does this make sense and is there a way to do it?
@bartlettroscoe https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1397Should non-MPI serial builds be part of "clean" build track?2017-06-14T14:30:35ZJames WillenbringShould non-MPI serial builds be part of "clean" build track?*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @maherou
**Description:**
Should non-MPI "Serial" builds be part of the "Clean" dashboard track?
Currently 2 of the 3 "Clean" builds up on CDash:
* Linux-GCC-4.7.2-S...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @maherou
**Description:**
Should non-MPI "Serial" builds be part of the "Clean" dashboard track?
Currently 2 of the 3 "Clean" builds up on CDash:
* Linux-GCC-4.7.2-SERIAL_OPT_DEV
* Linux-gcc-4.9.3-SERIAL_Release_gcc_4.9.3__DEV
* Linux-gcc-4.9.3-MPI_Release_gcc_4.9.3_openmpi_1.8.7_DEV
are non-MPI SERIAL builds. Why is that? What important Trilinos customer is relying on a non-MPI build of Trilinos?
The only builds that are immediately critical to Trilinos should be in the set of clean builds.
One example of the problem this causes is #1392.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1390Create plan to drop Trilinos support for C++98 preventing the usage of C++112017-12-19T23:01:13ZJames WillenbringCreate plan to drop Trilinos support for C++98 preventing the usage of C++11*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/teuchos, @trilinos/thyra, @trilinos/nox, @maherou
**Description:**
The requirement to maintain C++98 support for older packages like Teuchos, Thyra, NOX and othe...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @trilinos/teuchos, @trilinos/thyra, @trilinos/nox, @maherou
**Description:**
The requirement to maintain C++98 support for older packages like Teuchos, Thyra, NOX and others that are still being developed and need much more development in the near future, is creating a major capability and productivity impediment for projects like ATDM. (For example, the refactoring of Thyra to improve the design, usage, and performance of RTOps will require C++11.) But we can't use C++11 in these packages because there are still some Trilinos customers that still require that these packages build with GCC 4.4.7 and C++11 turned off. And just the usage of `auto` alone will significantly improve the development and maintenance of templated code. (And then there is the performance improvements of using move constructors and assignment operators, etc.)
To address this problem we could either, for example:
1) Require all Trilinos customers to upgrade their compilers to GCC 4.9.3 or newer to allow C++11 to be used in all Trilinos packages from Teuchos on down the dependency chain.
or:
2) Create a fork of Trilinos for C++98 packages needed by these customers and then allow the main Trilinos 'develop' and 'master' branches require C++11 for all packages from Teuchos on down the dependency chain. (This would require the Trilinos development team to continue to provide patches, releases, and address other issues on this fork, so this fork could not be completely static but it should see very little development.)
But eventually every Trilinos customer will have a C++11 compiler so eventually we will be going with option-1 so going with option-2 in the short-term may not be too bad.
Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1386Eliminate unnecessary rebuilds of Trilinos code on a reconfigure2017-06-10T14:48:49ZJames WillenbringEliminate unnecessary rebuilds of Trilinos code on a reconfigure*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @maherou, @rppawlo, @jhux2
**Description:**
It has been reported by several people (and in #1241) that some (or perhaps all) reconfigurations of Trilinos will trigger the ...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @maherou, @rppawlo, @jhux2
**Description:**
It has been reported by several people (and in #1241) that some (or perhaps all) reconfigurations of Trilinos will trigger the rebuild of a **lot** of object files, libraries and executables.
This story is to officially investigate this issue and try to resolve any problems that are discovered.
To help diagnose this, the Ninja build tool should be used since it can be used to trace why the build system triggers the rebuilds of each object file.
Reduce build times for Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1378Upgrade Trilinos for replacement of PARSE_ARGUMENTS() in TriBITS (TriBITSPub/...2018-11-13T16:25:04ZJames WillenbringUpgrade Trilinos for replacement of PARSE_ARGUMENTS() in TriBITS (TriBITSPub/TriBITS#181)*Created by: bartlettroscoe*
This story is to track the work to update Trilinos to use an updated version of TriBITS that removes the usage of the home-grown `PARSE_ARGUMENTS()` with the built-in CMake function `CMAKE_PARSE_ARGUMENTS()`...*Created by: bartlettroscoe*
This story is to track the work to update Trilinos to use an updated version of TriBITS that removes the usage of the home-grown `PARSE_ARGUMENTS()` with the built-in CMake function `CMAKE_PARSE_ARGUMENTS()` (see TriBITSPub/TriBITS#181).
When I tried the upgrade, I got a bunch of configure warnings and errors due to stronger checking provided by `CMAKE_PARSE_ARGUMENTS()`.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1375Remove Phalanx and Panzer from -Werror GCC 4.7.2 build2017-06-01T15:50:11ZJames WillenbringRemove Phalanx and Panzer from -Werror GCC 4.7.2 build*Created by: jwillenbring*
CC: @bartlettroscoe @william76
@rppawlo requested Phalanx and Panzer be removed from the GCC 4.7.2 Werror build. Phalanx and Panzer should be included in the 4.9 build.*Created by: jwillenbring*
CC: @bartlettroscoe @william76
@rppawlo requested Phalanx and Panzer be removed from the GCC 4.7.2 Werror build. Phalanx and Panzer should be included in the 4.9 build.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1363Upgrade minimum support GCC from 4.7.2 with C++11 to something higher (4.8.4 ...2017-06-26T17:00:53ZJames WillenbringUpgrade minimum support GCC from 4.7.2 with C++11 to something higher (4.8.4 or 4.9.3)?*Created by: bartlettroscoe*
**Next Action Status:**
Looks like some customers need GCC 4.8.4 with C++11 Trilinos currently. Next: Decide to make the downgrade the CI server from GCC 4.9.3 back to GCC 4.8.4 (which currently passes t...*Created by: bartlettroscoe*
**Next Action Status:**
Looks like some customers need GCC 4.8.4 with C++11 Trilinos currently. Next: Decide to make the downgrade the CI server from GCC 4.9.3 back to GCC 4.8.4 (which currently passes the full CI test suite) ...
**CC:** @trilinos/framework
**Description:**
Maintaining support for GCC 4.7.2 puts a lot of constraints on the C++11 code that you can write and is holding back Trilinos development (see #1002). This story is to remove testing and support for GCC 4.7.2 and upgrade to GCC 4.8.x or newer (GCC 4.9.3 would be better given that is what Sierra uses).
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1359TriBITS: application access to TPL_Netcdf_PARALLEL2017-05-24T14:18:26ZJames WillenbringTriBITS: application access to TPL_Netcdf_PARALLEL*Created by: ibaned*
In the Albany application, we would like to be able to detect whether Trilinos was built with the `TPL_Netcdf_PARALLEL` flag `ON`. What is the best way to do that ?
@bartlettroscoe @trilinos/framework*Created by: ibaned*
In the Albany application, we would like to be able to detect whether Trilinos was built with the `TPL_Netcdf_PARALLEL` flag `ON`. What is the best way to do that ?
@bartlettroscoe @trilinos/frameworkhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1344How to contribute to wiki pages2017-09-06T19:47:50ZJames WillenbringHow to contribute to wiki pages*Created by: tjfulle*
@bartlettroscoe, how does one contribute to the wiki pages? It don't see a way to fork the wiki so that I can submit a PR. Nor do I see any create new page/edit page buttons. Should I just clone and send a diff ...*Created by: tjfulle*
@bartlettroscoe, how does one contribute to the wiki pages? It don't see a way to fork the wiki so that I can submit a PR. Nor do I see any create new page/edit page buttons. Should I just clone and send a diff to someone?
It seems valuable for new developer, such as myself, to give input to the wiki (at least to the new developer/building Trilinos pages) while the pain of ramping up is fresh on their mind...https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1341Eliminate warnings in CI build coming from mpi.h with GCC 4.9.3 and OpenMPI f...2017-06-27T14:51:00ZJames WillenbringEliminate warnings in CI build coming from mpi.h with GCC 4.9.3 and OpenMPI from 1.6.5*Created by: bartlettroscoe*
**Next Action Status:**
Adding `-isystem` for OpenMPI 1.6. include dir makes warnings go away locally but not for CTest -S script. Asked SEMS if they could patch mpi.h file (but unknown when that might h...*Created by: bartlettroscoe*
**Next Action Status:**
Adding `-isystem` for OpenMPI 1.6. include dir makes warnings go away locally but not for CTest -S script. Asked SEMS if they could patch mpi.h file (but unknown when that might happen). Next: Switch CI build to GCC 4.8.4 which does not emit the warnings?
**CC:** @trilinos/framework
**Description:**
With the upgrade to GCC 4.9.3 (see #1002), we are now getting a lot of warnings from OpenMPI 1.6.5 headers like:
```
In file included from /projects/sems/install/rhel6-x86_64/sems/compiler/gcc/4.9.3/openmpi/1.6.5/include/mpi.h:253:0,
from /scratch/rabartl/Trilinos.base/SEMSCIBuild/Trilinos/packages/teuchos/core/src/Teuchos_Time.hpp:56,
from /scratch/rabartl/Trilinos.base/SEMSCIBuild/Trilinos/packages/teuchos/core/src/Teuchos_Time.cpp:45:
/projects/sems/install/rhel6-x86_64/sems/compiler/gcc/4.9.3/openmpi/1.6.5/include/mpi_portable_platform.h:374:34: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
_STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
^
/projects/sems/install/rhel6-x86_64/sems/compiler/gcc/4.9.3/openmpi/1.6.5/include/mpi_portable_platform.h:374:63: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
_STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
^
```
such as you see, for example, in this CI iteration:
* http://testing.sandia.gov/cdash/viewBuildError.php?type=1&buildid=2902564
Looking at the new "Clean" build
Linux-gcc-4.9.3-MPI_Release_gcc_4.9.3_openmpi_1.8.7_DEV targeted for SIERRA, for example, at:
* http://testing.sandia.gov/cdash/index.php?project=Trilinos&parentid=2901291
perhaps our CI build should be upgraded to OpenMPI 1.8.7?
In any case, this story is to make these warnings go away so they don't spam Trilinos developers and CDash.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1335checkin-test.py no longer functions2017-06-14T14:15:03ZJames Willenbringcheckin-test.py no longer functions*Created by: csiefer2*
@bartlettroscoe
@bmpersc
The python checkin script no longer functions. It requires yaml_cpp, but cannot find it even if the associated sems module is loaded.*Created by: csiefer2*
@bartlettroscoe
@bmpersc
The python checkin script no longer functions. It requires yaml_cpp, but cannot find it even if the associated sems module is loaded.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1304Address basic stability of Trilinos 'develop' branch short-term2018-06-14T14:45:43ZJames WillenbringAddress basic stability of Trilinos 'develop' branch short-term*Created by: bartlettroscoe*
**Related to:** #1362
**Next Action Status:**
The auto PR testing process (#1155) is deployed and is working fairly well to stabilize 'develop' (at least as good or better than the checkin-test-sems....*Created by: bartlettroscoe*
**Related to:** #1362
**Next Action Status:**
The auto PR testing process (#1155) is deployed and is working fairly well to stabilize 'develop' (at least as good or better than the checkin-test-sems.sh script did). Further improvements will be worked in other issues.
**Description:**
This story is to discuss and decide how to address stability problems of the Trilinos 'develop' branch in the short term. I know there is a long-term plan to use a PR model (see #1155) but since there are no updates or ETA on that, we need to address stability issues faster than that.
Currently there have been a good deal of stability problems of the Trilinos 'develop' branch, even with the basic CI build linked to from:
* https://github.com/trilinos/Trilinos/wiki/Policies--%7C-Testing#post_push_ci_testing
and the "Clean" builds shown here:
* http://testing.sandia.gov/cdash/index.php?project=Trilinos&display=project&filtercount=2&showfilters=1&filtercombine=and&field1=groupname&compare1=61&value1=Clean&field2=buildstarttime&compare2=84&value2=now
The "Clean" builds have never been clean in the entire history of the track.
Some very recent examples of failures causing this are described in #1290 and #1301. These have broken the standard CI build and the "Clean" builds continuously since May 4 (and it is still broken as I type this).
We need a strategy to improve stability right now. I have been helping people set up to use the [checkin-test-sems.sh](https://github.com/trilinos/Trilinos/wiki/Policies-%7C-Safe-Checkin-Testing) script to test and push their changes. I would estimate that a large percentage of the failures (and 100% of the CI failures) seen on CDash would be avoided by usage of the checkin-test-sems.sh script.
**CC:** @trilinos/framework Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1298Move prototype parameterized tests to main repo2017-05-10T17:29:15ZJames WillenbringMove prototype parameterized tests to main repo*Created by: bmpersc*
The prototype parameterized build has been working well for a while so it is time to move it into the Trilinos repo and update all the builds that are using it to use the Trilinos repo instead of the prototype repo.*Created by: bmpersc*
The prototype parameterized build has been working well for a while so it is time to move it into the Trilinos repo and update all the builds that are using it to use the Trilinos repo instead of the prototype repo.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1294Remove all failures in "Clean" track builds.2017-10-11T13:53:14ZJames WillenbringRemove all failures in "Clean" track builds.*Created by: jwillenbring*
Done for this ticket means all "Clean" track builds shown on
[http://testing.sandia.gov/cdash/index.php?project=Trilinos&date=2017-05-07](http://testing.sandia.gov/cdash/index.php?project=Trilinos&date=201...*Created by: jwillenbring*
Done for this ticket means all "Clean" track builds shown on
[http://testing.sandia.gov/cdash/index.php?project=Trilinos&date=2017-05-07](http://testing.sandia.gov/cdash/index.php?project=Trilinos&date=2017-05-07)
are 100% passing.Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1288Trilinos-Xyce testing for C++11=OFF is failing2017-05-08T21:42:41ZJames WillenbringTrilinos-Xyce testing for C++11=OFF is failing*Created by: hkthorn*
@trilinos/framework @jwillenbring @bmpersc It looks like the environment issues with the Trilinos-Xyce testing were fixed, but the nightly testing of this build still does not complete.*Created by: hkthorn*
@trilinos/framework @jwillenbring @bmpersc It looks like the environment issues with the Trilinos-Xyce testing were fixed, but the nightly testing of this build still does not complete.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1247Create automated ATDM build of Trilinos on shiller submitting to Trilinos CDa...2018-01-11T19:20:27ZJames WillenbringCreate automated ATDM build of Trilinos on shiller submitting to Trilinos CDash site*Created by: bartlettroscoe*
**Next Action Status:**
Reproduced the configure of Trilinos+Drekar on 'shiller'. Next: Create refactored files and scripts and put into Trilinos git repo ...
**Description:**
This story is assoica...*Created by: bartlettroscoe*
**Next Action Status:**
Reproduced the configure of Trilinos+Drekar on 'shiller'. Next: Create refactored files and scripts and put into Trilinos git repo ...
**Description:**
This story is assoicated with #1246 and that is to drive the creation of these common ATDM configuration files and scripts while getting an automated build of Trilinos for ATDM set up on shiller with CUDA/GPUs. This will be followed by other stories for getting common configuration files and automated builds set up for other ATDM platforms.
These files will be copied and refactored from those that exist for Trilinos+Drekar on shiller. The existing configure scripts in for Trilinos+Drekar will be refactored to use these new scripts so there is no duplication.
**Definition of Done:**
* A set of standard configuration files and scripts exists in the Trilinos git repo to configure Trilinos for ATDM on Shiller
* The Drekar build scripts are refactored to use these.
* An automated nightly build for Trilinos for the packages used by Drekar and EMPIRE is running and posting to the Trilinos CDash site.
**CC:** @trilinos/framework, @bathmatt, @rppawlo, @kruger
Get Trilinos builds and testing for ATDM under coordinated version control