Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2017-12-19T23:01:13Zhttps://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/1628CUDA config & build are broken2017-08-21T00:44:24ZJames WillenbringCUDA config & build are broken*Created by: mhoemmen*
@trilinos/framework
I'm not sure if this is a Kokkos (@crtrott, @dsunder, @ibaned ) issue, a Trilinos issue, or a SEMS issue (@jgfouca), but something recently (as of last week) totally messed up CUDA builds f...*Created by: mhoemmen*
@trilinos/framework
I'm not sure if this is a Kokkos (@crtrott, @dsunder, @ibaned ) issue, a Trilinos issue, or a SEMS issue (@jgfouca), but something recently (as of last week) totally messed up CUDA builds for me. This is blocking #1569, #1606, #1367, #1623, and a bunch of other issues. It is delaying testing and acceptance of @tjfulle 's and @brian-kelley 's hard work.
When I run `make`, I get this (replace `...` here and elsewhere with the path to Trilinos' source directory):
```
[ 0%] Building CXX object packages/kokkos/core/src/CMakeFiles/kokkoscore.dir/impl/Kokkos_hwloc.cpp.o
cd .../../Trilinos/CHECKIN-CUDA-8.0/MPI_DEBUG_REAL/packages/kokkos/core/src && /projects/sems/install/rhel6-x86_64/sems/compiler/gcc/5.3.0/base/bin/g++ -Dkokkoscore_EXPORTS -pedantic -Wall -Wno-long-long -Wwrite-strings -Wall -std=c++11 -expt-extended-lambda -std=c++11 -fopenmp -g -O0 -fPIC -I/scratch/prj/Trilinos/CHECKIN-CUDA-8.0/MPI_DEBUG_REAL -I.../../Trilinos/CHECKIN-CUDA-8.0/MPI_DEBUG_REAL/packages/kokkos/core/src -I.../Trilinos/packages/kokkos/core/src -I/projects/sems/install/rhel6-x86_64/kokkos/compiler/cuda/8.0.44/include -o CMakeFiles/kokkoscore.dir/impl/Kokkos_hwloc.cpp.o -c .../Trilinos/packages/kokkos/core/src/impl/Kokkos_hwloc.cpp
In file included from .../Trilinos/packages/kokkos/core/src/impl/Kokkos_hwloc.cpp:50:0:
.../Trilinos/packages/kokkos/core/src/Kokkos_Macros.hpp:170:40: error: ‘__device__’ does not name a type
#define KOKKOS_INLINE_FUNCTION __device__ __host__ inline
^
.../Trilinos/packages/kokkos/core/src/impl/Kokkos_Error.hpp:73:1: note: in expansion of macro ‘KOKKOS_INLINE_FUNCTION’
KOKKOS_INLINE_FUNCTION
^
```
Notice that it's running `g++` directly, not `nvcc` or `mpicxx` or anything like that. I am using the SEMS modules on my workstation, `artemis`. Here is the list of loaded modules:
```
$ module list
Currently Loaded Modulefiles:
1) sems-env 3) sems-cmake/3.3.2 5) kokkos-cuda/8.0.44
2) kokkos-env 4) sems-gcc/5.3.0 6) kokkos-openmpi/2.0.1/cuda
```
Here is the output of `nvcc --version`:
```
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Sun_Sep__4_22:14:01_CDT_2016
Cuda compilation tools, release 8.0, V8.0.44
```
Here is the output of `echo $OMPI_CXX`:
```
.../Trilinos/packages/kokkos/config/nvcc_wrapper
```
Here is the output of `mpicxx --version`:
```
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Sun_Sep__4_22:14:01_CDT_2016
Cuda compilation tools, release 8.0, V8.0.44
```
Here are my relevant CMake options:
```
-D Trilinos_ENABLE_EXPLICIT_INSTANTIATION:BOOL=ON
-D BUILD_SHARED_LIBS:BOOL=ON
-D Trilinos_ENABLE_OpenMP:BOOL=ON
-D Trilinos_SHOW_DEPRECATED_WARNINGS:BOOL=ON
-D Trilinos_ENABLE_Fortran:BOOL=OFF
-D CMAKE_VERBOSE_MAKEFILE:BOOL=ON
-D CMAKE_Fortran_LINK_EXECUTABLE:FILEPATH=""
-D TPL_ENABLE_CUDA:BOOL=ON
-D Kokkos_ENABLE_Cuda_UVM:BOOL=ON
-D Tpetra_INST_CUDA:BOOL=ON
-D Kokkos_ENABLE_Cuda_Lambda:BOOL=ON
-D Kokkos_ENABLE_CXX11_DISPATCH_LAMBDA:BOOL=ON
-D CMAKE_CXX_FLAGS:STRING="-Wall -std=c++11 -expt-extended-lambda"
-D CMAKE_BUILD_TYPE:STRING=DEBUG
-D Kokkos_ENABLE_DEBUG:BOOL=ON
-D Teuchos_ENABLE_DEBUG:BOOL=ON
-D CMAKE_CXX_FLAGS_DEBUG:STRING="-Os"
-D Tpetra_INST_SERIAL:BOOL=OFF
-D Teuchos_ENABLE_COMPLEX:BOOL=OFF
-D Trilinos_ENABLE_COMPLEX_FLOAT:BOOL=OFF
-D Trilinos_ENABLE_COMPLEX_DOUBLE:BOOL=OFF
```
I have the same trouble with my CUDA 7.5 build. Thus, this issue also hinders #1278, because we are supposed to keep supporting CUDA 7.5 until at least the next minor release.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1645Dashboard failures, possibly due to incorrectly configured test platform2017-10-27T04:18:34ZJames WillenbringDashboard failures, possibly due to incorrectly configured test platform*Created by: mhoemmen*
@trilinos/framework @trilinos/tpetra
ascic141, build name `Linux-gcc-4.9.3-Sierra_MPI_release_DEV_ETI_SERIAL-ON_OPENMP-OFF_PTHREAD-ON_CUDA-OFF_COMPLEX-ON`, has 21 Tpetra test failures. Here is the latest list...*Created by: mhoemmen*
@trilinos/framework @trilinos/tpetra
ascic141, build name `Linux-gcc-4.9.3-Sierra_MPI_release_DEV_ETI_SERIAL-ON_OPENMP-OFF_PTHREAD-ON_CUDA-OFF_COMPLEX-ON`, has 21 Tpetra test failures. Here is the latest list:
https://testing.sandia.gov/cdash/viewTest.php?onlyfailed&buildid=3072459
They all generate the following output:
```
p=0: *** Caught standard std::exception of type 'std::runtime_error' :
Constructing View and initializing data with uninitialized execution space
Traceback functionality not available
```
I was wondering at first whether the tests were using the default execution space instead of their Node's execution space. However, check out the following failing test output:
https://testing.sandia.gov/cdash/testDetails.php?test=40862107&build=3072459
This is supposed to be for the default Node, yet the test is failing. It looks like this could be a broken configuration.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/2068Dashboard ride CUDA build fails in config; can't find BLAS2017-12-09T20:57:02ZJames WillenbringDashboard ride CUDA build fails in config; can't find BLAS*Created by: mhoemmen*
The Dashboard CUDA build for ride does not pass the configure process, because it fails to find the BLAS:
https://testing.sandia.gov/cdash/viewConfigure.php?buildid=3264127
@trilinos/framework
## Expecta...*Created by: mhoemmen*
The Dashboard CUDA build for ride does not pass the configure process, because it fails to find the BLAS:
https://testing.sandia.gov/cdash/viewConfigure.php?buildid=3264127
@trilinos/framework
## Expectations
Working ride Dashboard build.
## Current Behavior
The ride build doesn't get through the configure process, because it can't find the BLAS.
## Motivation and Context
Applications use Trilinos on ride with CUDA, and need to see a working Dashboard build.
## Possible Solution
Talk to @micahahoward et al. to see how they build on ride. Match their CMake configuration.
## Steps to Reproduce
1. Gaze upon the Dashboard
2. Behold, the ride build reports an error at configure time
## Related Issues
* Related to #1753, #1699, #1675, #1574, #1216
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/452Decide on how to handle multi-repos with Trilinos both short-term and long-term2016-08-29T16:42:49ZJames WillenbringDecide on how to handle multi-repos with Trilinos both short-term and long-term*Created by: bartlettroscoe*
**Next Action Status:**
???
**CC:** @trilinos/framework
**Blocking:** #440, #176
**Description:**
When Trilinos was trimmed down and moved to GitHub, several extra repos were split out into their own r...*Created by: bartlettroscoe*
**Next Action Status:**
???
**CC:** @trilinos/framework
**Blocking:** #440, #176
**Description:**
When Trilinos was trimmed down and moved to GitHub, several extra repos were split out into their own repos like MOOCHO, Sundance, CTrilinos, ForTrilinos, Mesquite, etc. There was a plan for managing these extra repos using the support for extra repos added for TriBITS to support CASL VERA development in the Goolge Doc [Proposal for trimming down Trilinos repo](https://docs.google.com/document/d/1hbki9KN4ErCChWcvAFBnOsJcPLuDJtPi8xaNq3ETyRo/edit?usp=drive_web) which was started in late 2014 or so. Given that Trilinos was split up, I (@bartlettroscoe) assumed that the plan listed in that document was a reasonable approach to get these extra repos for inserted packages back into automated testing and for distribution in Trilinos releases (because CASL VERA has been doing this for years). Based on this assumption, I created the issue #176 to get this working for Trilinos, CCing the other Trilinos Framework team members. I think did some work on this approach and got many of these inserted packages back under automated testing and added full support for the usage of the TriBITS `clone_extra_repos.py` and `gitdist` scripts. However, my assumption that there was agreement to use the the TriBITS approached used by CASL VERA as an initial way to address multiple repositories in Trilinos was not founded. It seems that others did not agree with that decision.
Therefore, this Trilinos GitHub ticket is to drive and document the discussion of this topic and the decisions on how Triilnos should deal with multiple repos, both short-term and long-term.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1745Define labels and rules for Trilinos application issues and metrics2018-11-30T11:23:42ZJames WillenbringDefine labels and rules for Trilinos application issues and metrics*Created by: ibaned*
Please see the discussion between https://github.com/trilinos/Trilinos/issues/1304#issuecomment-329885910 and https://github.com/trilinos/Trilinos/issues/1304#issuecomment-329918877 where I propose the following:
...*Created by: ibaned*
Please see the discussion between https://github.com/trilinos/Trilinos/issues/1304#issuecomment-329885910 and https://github.com/trilinos/Trilinos/issues/1304#issuecomment-329918877 where I propose the following:
> create a few extra issues labels besides "bug", namely "compile error (Trilinos)", "compile error (application)", "compile warning (Trilinos)", "compile warning (application)", "test failure (Trilinos)", "test failure (application)". Then we can collect statistics on how many issues with each label were opened in a particular period of time. I would also expand "(Trilinos)" to be either "(Trilinos/develop)" or "(Trilinos/master)"
Note @bartlettroscoe 's observation:
> before we define any more labels I think we need to better organize them along the lines of #1619.
@maherou @jwillenbring Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/2563Delete old autotester messages2018-04-17T15:43:41ZJames WillenbringDelete old autotester messages*Created by: cgcgcg*
@trilinos/framework
## Expectations
It would be great if the autotester would delete old messages that are not useful anymore. In particular, once a build is done, the message about the start of the build is ...*Created by: cgcgcg*
@trilinos/framework
## Expectations
It would be great if the autotester would delete old messages that are not useful anymore. In particular, once a build is done, the message about the start of the build is superfluous.
More generally, all messages could be condensed into a single message that gets updated. This would avoid having pull requests getting flooded with a bunch of autotester runs..https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1154Deploy automated develop to master branch testing2017-10-04T16:37:23ZJames WillenbringDeploy automated develop to master branch testing*Created by: jwillenbring*
@trilinos/framework
@allevin has completed revisions toward a capability that will allow us to automate the testing of the develop branch to determine if it is safe to promote that version of code to the m...*Created by: jwillenbring*
@trilinos/framework
@allevin has completed revisions toward a capability that will allow us to automate the testing of the develop branch to determine if it is safe to promote that version of code to the master branch.
We need to deploy this capability. Here are some proposed tasks for discussion for completion of this story:
1. Fully deploy the capability on Aaron's fork of Trilinos. This will allow us to see the capability in action a couple of times from beginning to end. This should use the complete infrastructure intended for the eventually full deployment, including Jenkins.
2. Test the new capability using the primary Trilinos repository, but temporarily disable the push to master.
3. Fully deploy, including the push to master.
Please comment on this approach.Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/501Develop and use git commit template for Trilinos repo2017-05-15T12:56:09ZJames WillenbringDevelop and use git commit template for Trilinos repo*Created by: bartlettroscoe*
**CC:** @trilinos/framework
**Description:**
Using a commit template has been shown on other projects to help make commit messages more consistent and contain the proper information.
This story is to cre...*Created by: bartlettroscoe*
**CC:** @trilinos/framework
**Description:**
Using a commit template has been shown on other projects to help make commit messages more consistent and contain the proper information.
This story is to create a git commit template that will be used by default for all Trilinos commits.
**Definition of Done:**
Git commit template is installed and presented for all Trilinos commits (but the commit author can modify the commit in the editor before the commit is created).
**Tasks:**
1. Learn and document how a git commit template works (see [here](https://github.com/TriBITSPub/TriBITS/issues/138#issuecomment-233959791)) [Done]
2. Develop template for a Trilinos commits (i.e. on a Google Doc) (see [below](https://github.com/trilinos/Trilinos/issues/501#issuecomment-233965160)) ... IN PROGRESS ...
3. Develop automated process for installing git commit hooks (e.g. as a side-effect of running the CMake configure) (see [here](https://github.com/TriBITSPub/TriBITS/issues/138#issuecomment-233962167)) ... Waiting to be worked ...
Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3628Did CMake 3.10.0 requirement break the check-in test script?2018-10-31T23:57:31ZJames WillenbringDid CMake 3.10.0 requirement break the check-in test script?*Created by: mhoemmen*
@trilinos/framework @bartlettroscoe
The latest changes that require CMake 3.10.0 seem to have broken the check-in test script. I invoked the script like this:
```
.../Trilinos/checkin-test.py --ctest-timeou...*Created by: mhoemmen*
@trilinos/framework @bartlettroscoe
The latest changes that require CMake 3.10.0 seem to have broken the check-in test script. I invoked the script like this:
```
.../Trilinos/checkin-test.py --ctest-timeout=400 --disable-packages=PyTrilinos,Claps,TriKota,Domi,STKSearch,Moertel,Shards --skip-case-no-email --allow-no-pull --enable-all-packages=off --default-builds= --extra-builds=MPI_DEBUG_EX --enable-packages=TpetraCore,Zoltan2,Amesos2 --configure
```
with the following modules loaded:
```
1) sems-env 3) sems-cmake/3.12.2 5) sems-openmpi/1.10.1 7) sems-boost/1.59.0/base 9) sems-hdf5/1.8.12/parallel 11) sems-zlib/1.2.8/base
2) kokkos-env 4) sems-gcc/4.9.3 6) sems-python/2.7.9 8) sems-superlu/4.3/base 10) sems-netcdf/4.4.1/exo_parallel 12) sems-parmetis/4.0.3/parallel
```
I get the following output:
```
...
B) Do the configuration with CMake (MPI_DEBUG_EX) ...
Running: rm CMakeCache.txt
Running: rm -rf CMakeFiles
Running: ./do-configure
Writing console output to file configure.out ...
Runtime for command = 0.302733 minutes
Configure failed returning 1!
Traceback (most recent call last):
File "/scratch/prj/Trilinos/Trilinos/cmake/tribits/ci_support/CheckinTest.py", line 1563, in runBuildTestCase
raise Exception("Configure failed!")
Exception: Configure failed!
E) Analyze the overall results and send email notification (MPI_DEBUG_EX) ...
E.1) Determine what passed and failed ...
The pull step was not performed!
The configure FAILED!
```
Should I consider the check-in test script dead? It was a useful tool & I'm sad to see it go.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1355Disable external repos for parameterized builds2017-05-23T17:09:04ZJames WillenbringDisable external repos for parameterized builds*Created by: bmpersc*
Based on a discussion regarding sundance failures on the clean build the Framework team decided it was best to just disable all of the packages that come from external repos for non-specialized builds.
Currently...*Created by: bmpersc*
Based on a discussion regarding sundance failures on the clean build the Framework team decided it was best to just disable all of the packages that come from external repos for non-specialized builds.
Currently there is an option in the configure "Trilinos_EXTRA_REPOSITORIES" that is set to the empty string, but this doesn't seem to be affecting what external repos are pulled in. This needs to be investigated on how to prevent the the external repos from being automatically pulled in.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1338Disable Fortran by default for Trilinos on Mac OSX machines as well?2017-05-18T19:27:07ZJames WillenbringDisable Fortran by default for Trilinos on Mac OSX machines as well?*Created by: bartlettroscoe*
**CC:** @trilinos/developers, @trilinos/framework
**Description:**
Given that most Mac OSX machines don't have a working Fortran compiler by default, should we change the CMake logic to disable Fortran...*Created by: bartlettroscoe*
**CC:** @trilinos/developers, @trilinos/framework
**Description:**
Given that most Mac OSX machines don't have a working Fortran compiler by default, should we change the CMake logic to disable Fortran by default on Mac OSX machines? That will technically break backward compatibility but given the you don't need Fortran to get a lot out of Trilinos, I am not sure how many users would notice.
I am asking this since I am modifying TriBITS to fix a defect in how it handles the default for `<Project>_ENABLE_Fortran` and I want to move all special platform-specific logic to the project itself. Since I will be updating Trilinos/CMakeLists.txt for this refactoring, I thought I would ask about since I could make this change at the same time.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4238Disable Fortran in one of the Trilinos PR builds2019-01-31T20:57:09ZJames WillenbringDisable Fortran in one of the Trilinos PR builds*Created by: bartlettroscoe*
CC: @trilinos/framework, @mhoemmen, @rppawlo, @bathmatt, @jmgate, @fryeguy52
There are several projects that disable Fortran when building Trilinos. Currently, the EMPIRE ATDM Trilinos configuration dis...*Created by: bartlettroscoe*
CC: @trilinos/framework, @mhoemmen, @rppawlo, @bathmatt, @jmgate, @fryeguy52
There are several projects that disable Fortran when building Trilinos. Currently, the EMPIRE ATDM Trilinos configuration disables Fortran. (But that will chance once we fully merge the SPARC and EMPIRE ATDM Trilinos configurations since the SPARC configuration enables Fortran.) The Drekar developers disable Fortran in their configurations (which is not likely to change). Also, many people who build on Macs disable Fortran (since Macs don't come with a Fortran compiler by default).
Therefore, it is important for Trilinos to support a Fortran-less configuration and build. Therefore, at least one of the Trilinos PR builds needs to set `Trilinos_ENABLE_Fortran=OFF`.
Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/1751Discuss and document workflow for directly snapshotting SEACAS into Trilinos ...2018-06-26T12:49:47ZJames WillenbringDiscuss and document workflow for directly snapshotting SEACAS into Trilinos to better serve ATDM*Created by: bartlettroscoe*
**Next Action Status:**
@gdsjaar to implement agreed to workflow on SEACAS github site then start doing new workflow ...
**CC:** @trilinos/framework, @gsjaardema
**Description:**
This story is t...*Created by: bartlettroscoe*
**Next Action Status:**
@gdsjaar to implement agreed to workflow on SEACAS github site then start doing new workflow ...
**CC:** @trilinos/framework, @gsjaardema
**Description:**
This story is to document a discussion and the final workflow for allowing @gsjaardema to directly SEACAS directly into Trilinos/packages/seacas/ in addition to shapshotting SEACAS into Sierra.base/seacas/ and then having that snapshotted from ther into Trilinos/packages/seacas/. The nature of the snapshotting process (i.e. never a merge) eliminates the potential for merge conflicts that might make the snapshotting from Sierra.base/seacas/ to Trilinos/packages/seacas/ more difficult. And this would allow @gsjaardema control to address issues for ATDM customers very quickly and simplify the version control and configuration of Trilinos for ATDM customers. For more background and discussion, see:
* https://software-srn.sandia.gov/jira/browse/SPAR-277
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1740Discuss, refine, and document subteam/subproject development branches2017-09-29T14:18:39ZJames WillenbringDiscuss, refine, and document subteam/subproject development branches*Created by: bartlettroscoe*
**CC:** @dridzal, @jwillenbring, @maherou
**Description:**
This story is to document a discussion about the subteam/subproject development workflow that I helped the ROL team to set up and how to gener...*Created by: bartlettroscoe*
**CC:** @dridzal, @jwillenbring, @maherou
**Description:**
This story is to document a discussion about the subteam/subproject development workflow that I helped the ROL team to set up and how to generalize it and document it for the benefit of other Trilinos development subteams.
**Definition of Done:**
ToDo: Fill in once discussion is farther along so we can better scope this out
**Tasks:**
* Have initial discussion ...
* Decide on concrete "definition of done" and set of tasks to complete ...
* ???
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1877Do automated testing for all Trilinos packages that are being released2017-10-20T12:35:30ZJames WillenbringDo automated testing for all Trilinos packages that are being released*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @maherou
**Description:**
It appears that there are packages that are going out with Trilinos releases that are not included in any of the automated builds of Trilinos, in...*Created by: bartlettroscoe*
**CC:** @trilinos/framework, @maherou
**Description:**
It appears that there are packages that are going out with Trilinos releases that are not included in any of the automated builds of Trilinos, including the release branch builds. For example, MOOCHO appears to have been released with Trilinos 12.12 but it does not appear to be tested in any automated builds of Trilinos as shown by, for example:
* https://testing.sandia.gov/cdash/index.php?project=Trilinos&date=2017-10-19&subproject=MOOCHO
We can't support packages in releases that don't have any automated testing.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/1293Document information concerning Clean, Nightly, and Specialized tracks2018-02-12T20:58:34ZJames WillenbringDocument information concerning Clean, Nightly, and Specialized tracks*Created by: jwillenbring*
@william76
I need to document the definition of, qualifications for, and process for moving between the 3 new tracks that we are dividing the Nightly track into for automated testing. Definition of done fo...*Created by: jwillenbring*
@william76
I need to document the definition of, qualifications for, and process for moving between the 3 new tracks that we are dividing the Nightly track into for automated testing. Definition of done for this story is:
Trilinos GitHub wiki page exists listing
--Three develop branch testing tracks - Clean, Nightly, and specialized, with a description of each track.
--Process for moving from one track to another.Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/479Domi web presence missing2016-07-01T13:56:34ZJames WillenbringDomi web presence missing*Created by: bmpersc*
The Domi package doesn't have any pages on the Trilinos.org site currently. Bill Spotz sent the following email regarding Domi's web presence.
Jim, Brent,
I assume this just got buried in the normal course of thi...*Created by: bmpersc*
The Domi package doesn't have any pages on the Trilinos.org site currently. Bill Spotz sent the following email regarding Domi's web presence.
Jim, Brent,
I assume this just got buried in the normal course of things, so I am going to nag again. Domi is not a listed package on the trilinos.org site, but it is officially released, so it should be. I don't really read perl, so it isn't obvious to me if I/we modify doc/build_docs.pl or some other database-type file to do this. Domi has a doc/build_docs script, but that doesn't seem to be sufficient. What else needs to be done?
Thanks,
Bill
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3447download for Trilinos 12.12.1 is broken?2018-09-20T16:12:53ZJames Willenbringdownload for Trilinos 12.12.1 is broken?*Created by: boegel*
When I try to download Trilinos 12.12.1 via https://trilinos.org/download/, I end up with a broken link.
I considered downloading from https://github.com/trilinos/Trilinos/releases instead, but the source tarball...*Created by: boegel*
When I try to download Trilinos 12.12.1 via https://trilinos.org/download/, I end up with a broken link.
I considered downloading from https://github.com/trilinos/Trilinos/releases instead, but the source tarball tagged there for 12.12.1 seems to be something entirely different (e.g. `CTrilinos` is not in there).
Is the broken download via the website a known problem?
Is there another way to download the same `trilinos-12.12.1-Source.tar.gz` that was available via https://trilinos.org/download?
@trilinos/packagehttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/45Download with mandatory sign-up2016-05-19T23:32:19ZJames WillenbringDownload with mandatory sign-up*Created by: nschloe*
There are many straightforward ways to get Trilinos nowadays:
- `git clone` from GitHub
- [download a release from GitHub](https://github.com/trilinos/Trilinos/releases)
- get it from [Debian](https://tracker.debia...*Created by: nschloe*
There are many straightforward ways to get Trilinos nowadays:
- `git clone` from GitHub
- [download a release from GitHub](https://github.com/trilinos/Trilinos/releases)
- get it from [Debian](https://tracker.debian.org/pkg/trilinos)
- get it from the [nightly PPA](https://launchpad.net/~nschloe/+archive/ubuntu/trilinos-nightly/)
Oh, and of course the [official download page](https://trilinos.org/download/) which [requires you to sign up before download](https://trilinos.org/oldsite/download/login.html?tid=tr12042bz2). Rather than helping the distribution of Trilinos, the sign-up hinders it. The gain that one supposedly gets from that is a user statistics, but in the light of the alternative download methods listed above, this statistic is practically worthless.
I suggest to remove the sign-up requirement from the download page.