Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2019-01-16T17:44:33Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3900Can't download trilinos2019-01-16T17:44:33ZJames WillenbringCan't download trilinos*Created by: VictorEijkhout*
Connecting to trilinos.csbsju.edu (trilinos.csbsju.edu)|152.65.160.65|:80... failed:*Created by: VictorEijkhout*
Connecting to trilinos.csbsju.edu (trilinos.csbsju.edu)|152.65.160.65|:80... failed:https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3857Framework: Add Wiki entry to describe useful email filters to help with githu...2018-11-19T22:53:59ZJames WillenbringFramework: Add Wiki entry to describe useful email filters to help with github spam*Created by: william76*
@trilinos/framework
A conversation came up today in our meeting with @bartlettroscoe about the email spam being sent out by github, especially since we started using the PR tester, which adds a few comments t...*Created by: william76*
@trilinos/framework
A conversation came up today in our meeting with @bartlettroscoe about the email spam being sent out by github, especially since we started using the PR tester, which adds a few comments to every PR, which generates an email each time. We thought a wiki article for Trilinos would be useful to go over useful email filter settings to help cut down the spam.
Generally speaking, I think what many people do is they filter out all the spam unless there is an @mention to them or a team they're on... but I think many people don't do this. So an article we can point people to would be useful.
This relates to some old issues #1674 #668 Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3832Framework: Add GCC 7.3 MPI dev->master and PR builds2018-12-05T17:18:40ZJames WillenbringFramework: Add GCC 7.3 MPI dev->master and PR builds*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/framework
<!---
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.
-->
We want to have dev->master and PR builds that use GCC 7.3.
## 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.
-->
Due to key customer requirements, GCC 7.2 is an important compiler for Trilinos to build cleanly with. The closest version we currently have on the SEMS NFS mount is 7.3, so we are going to use that, at least for the time being.
Eventually we want to add warnings as errors flags to this build too, but that will be covered in a separate ticket.
## 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.
-->
Definition of Done is that there is a PR build in place and a dev->master build in place, building cleanly (prior to the changes being tested in that instance).
## Possible Solution
<!---
Not obligatory, but suggest a fix for the bug or documentation, or suggest
ideas on how to implement the addition or change.
-->
1) Create files for GCC 7.3 analogous to Trilinos/cmake/std/PullRequestLinuxGCC4.9.3TestingSettings.cmake
Trilinos/cmake/std/sems/PullRequestGCC4.9.3TestingEnv.sh
and get those files into the develop branch
2) Modify the autotester config file for dev->master testing to include this build and run the build once to detect any issues. It might be good to set up a parameterized build for 7.3 to find most issues before doing this.
3) Once the dev->master build is clean, repeat the process at the PR level.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3813PR build Trilinos_pullrequest_gcc_4.9.3_SERIAL and the nightly "Clean" build ...2018-11-06T21:47:30ZJames WillenbringPR build Trilinos_pullrequest_gcc_4.9.3_SERIAL and the nightly "Clean" build Linux-gcc-4.9.3-SERIAL_Release_gcc_4.9.3__DEV are not the same*Created by: bartlettroscoe*
CC: @dridzal, @crtrott, @srajama1
@trilinos/framework,
It looks like the PR build `Trilinos_pullrequest_gcc_4.9.3_SERIAL` and the nightly "Clean" build `Linux-gcc-4.9.3-SERIAL_Release_gcc_4.9.3__DEV` ...*Created by: bartlettroscoe*
CC: @dridzal, @crtrott, @srajama1
@trilinos/framework,
It looks like the PR build `Trilinos_pullrequest_gcc_4.9.3_SERIAL` and the nightly "Clean" build `Linux-gcc-4.9.3-SERIAL_Release_gcc_4.9.3__DEV` are **NOT** the same!
The configuration for the PR build `Trilinos_pullrequest_gcc_4.9.3_SERIAL` for this PR shown [here](https://testing-vm.sandia.gov/cdash/viewConfigure.php?buildid=4141632) shows the Pthread TPL being explicitly enabled:
```
Explicitly enabled TPLs on input (by user): Pthread BLAS LAPACK Boost Zlib HDF5 Netcdf SuperLU BoostLib DLlib 10
...
Final set of enabled TPLs: Pthread BLAS LAPACK Boost Zlib HDF5 Netcdf SuperLU BoostLib DLlib 10
```
but the nightly "Clean" build `Linux-gcc-4.9.3-SERIAL_Release_gcc_4.9.3__DEV` shown [here](https://testing.sandia.gov/cdash-dev-view/viewConfigure.php?buildid=4142839) shows that the Pthread is **not** being explicitly enabled:
```
Explicitly enabled TPLs on input (by user): BLAS LAPACK Boost Zlib HDF5 Netcdf SuperLU BoostLib DLlib 9
...
Final set of enabled TPLs: BLAS LAPACK Boost Zlib HDF5 Netcdf SuperLU BoostLib X11 DLlib 10
```
This explains how code got onto 'develop' that was allowed to break the "Clean" non-MPI SERIAL build (see #3773 and #3803)
I thought the goal of the adding a (non-MPI) SERIAL PR build was to guarantee that the nightly "Clean" SERIAL would be clean?
Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3783PyTrilinos: How can I get the MPI include directory in a robust way?2018-10-31T18:44:06ZJames WillenbringPyTrilinos: How can I get the MPI include directory in a robust way?*Created by: wfspotz*
@trilinos/pytrilinos @trilinos/framework
## Expectations
In PyTrilinos, I have a python script that generates a SWIG interface file. That SWIG interface file needs to know where the `mpi.h` header file is, so ...*Created by: wfspotz*
@trilinos/pytrilinos @trilinos/framework
## Expectations
In PyTrilinos, I have a python script that generates a SWIG interface file. That SWIG interface file needs to know where the `mpi.h` header file is, so I can parse it and extract `MPI_VERSION`. I developed some logic to find it that worked for me, but it is not robust enough to work for all users. How can I obtain the MPI include path for finding `mpi.h` in a robust way?
## Current Behavior
In #3618 the user specifies his MPI configuration with
-D TPL_ENABLE_MPI:BOOL=ON
-D MPI_EXEC:FILEPATH=/opt/apps/xalt/0.6/bin/ibrun
but my script specifies the path to `mpi.h` incorrectly.
## Motivation and Context
Here is what I do. I start with a file `get_teuchos_rcp.py.in` that will get copied to the build directory with `cmake` variable substituted in. It has the following function defined to correctly interpret `cmake` boolean variables:
def cmake_bool(value):
if value.upper() in ("", "0", "FALSE", "N", "NO", "OFF"):
return False
return True
I then define python variable `WITH_MPI` (among many others) using
WITH_MPI = cmake_bool("${TPL_ENABLE_MPI}")
I then use this logic to define python variable `MPI_BASE_DIR`:
MPI_BASE_DIR = "${MPI_BASE_DIR}"
if WITH_MPI:
if MPI_BASE_DIR == "":
MPI_BIN_DIR = os.path.split("${MPI_CXX_COMPILER}")[0]
MPI_BASE_DIR = os.path.split(MPI_BIN_DIR)[0]
All this leads to supporting the following function:
def get_mpi_version():
header = os.path.join(MPI_BASE_DIR, "include", "mpi.h")
version = ""
for line in open(header, 'r').readlines():
if "MPI_VERSION" in line:
version = line.split()[2]
break
return version
But the assumption that `mpi.h` lives in `MPI_BASE_DIR/include` is wrong, because in my user's case, the actual path does not have an `include` suffix.
## Definition of Done
When the user in #3618 can build PyTrilinos at his installation, which is TACC.
## Possible Solution
Does the `cmake` logic that looks for MPI have logic that extracts the location of the `mpi.h` file? If not, could it be added?
## Related Issues
* Blocks #3618
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3778Framework: Autotester for master merge does not delete branches after merge2018-11-14T15:49:38ZJames WillenbringFramework: Autotester for master merge does not delete branches after merge*Created by: csiefer2*
The branch list is littered with merged branches like this guy:
master_merge_20181018_074226
After getting on my case about automatically generated branch proliferation, I'd like to return the favor :stuck_...*Created by: csiefer2*
The branch list is littered with merged branches like this guy:
master_merge_20181018_074226
After getting on my case about automatically generated branch proliferation, I'd like to return the favor :stuck_out_tongue:
@trilinos/framework
@william76 https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3761Framework: do Trilinos teams have repo read access?2018-11-17T01:57:06ZJames WillenbringFramework: do Trilinos teams have repo read access?*Created by: jhux2*
@trilinos/framework @srajama1 (product owner) @maherou @jwillenbring @bartlettroscoe
I would like to be able to assign the @trilinos/muelu team as a reviewer for MueLu-related PRs. According to [this](https://he...*Created by: jhux2*
@trilinos/framework @srajama1 (product owner) @maherou @jwillenbring @bartlettroscoe
I would like to be able to assign the @trilinos/muelu team as a reviewer for MueLu-related PRs. According to [this](https://help.github.com/articles/requesting-a-pull-request-review/) page, this should be possible _if_ the team has read permission for the repo.
Question: Do Trilinos teams have read permissions for the Trilinos repo? If not, would it be possible to allow teams read access, or is there a good reason for not doing so?https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3700Framework / TriBITS: download-cmake.py no longer points to a valid cmake2018-10-23T23:58:36ZJames WillenbringFramework / TriBITS: download-cmake.py no longer points to a valid cmake*Created by: csiefer2*
This guy: Trilinos/cmake/tribits/python_utils/download-cmake.py
Tries to download this: http://cmake.org/files/v2.8/cmake-3.10.0-Linux-i386.tar.gz
Which give ye ol' 404.
I discovered this in an initial se...*Created by: csiefer2*
This guy: Trilinos/cmake/tribits/python_utils/download-cmake.py
Tries to download this: http://cmake.org/files/v2.8/cmake-3.10.0-Linux-i386.tar.gz
Which give ye ol' 404.
I discovered this in an initial setups of nightly testing on one of my machines.
@bartlettroscoe https://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/3585Test Anasazi_Epetra_OrthoManagerGenTester_0_MPI_4 appears to be randomly fail...2019-04-02T18:21:50ZJames WillenbringTest Anasazi_Epetra_OrthoManagerGenTester_0_MPI_4 appears to be randomly failing in many builds including CI, PR, and ATDM builds*Created by: bartlettroscoe*
CC: @trilinos/framework, @trilinos/anasazi, @srajama1 (Trilinos Linear Solver Product Area Lead)
## Next Action Status
PR #4052 merged to 'develop' on 12/18/2018 but still failing after that. Next: Tr...*Created by: bartlettroscoe*
CC: @trilinos/framework, @trilinos/anasazi, @srajama1 (Trilinos Linear Solver Product Area Lead)
## Next Action Status
PR #4052 merged to 'develop' on 12/18/2018 but still failing after that. Next: Try to fix again?
## Description
It would seem that the test `Anasazi_Epetra_OrthoManagerGenTester_0_MPI_4` is very occasionally randomly failing in various builds. As shown in [this query](https://testing.sandia.gov/cdash-dev-view/queryTests.php?project=Trilinos&date=2018-10-09&filtercount=4&showfilters=1&filtercombine=and&field1=testname&compare1=61&value1=Anasazi_Epetra_OrthoManagerGenTester_0_MPI_4&field2=status&compare2=61&value2=failed&field3=details&compare3=64&value3=timeout&field4=buildstarttime&compare4=83&value4=2018-07-01), this test failed 10 times since 7/1/2018 in the builds:
* `Linux-GCC-4.8.4-MPI_RELEASE_DEBUG_SHARED_PT_OPENMP_CI` (post-push CI build): 1 time (today)
* `PR-XXXX-test-Trilinos_pullrequest_gcc_4.9.3-YYYY` (standard PR build): 4 times
* `PR-XXXX-test-Trilinos_pullrequest_gcc_4.8.4-YYYY` (standard PR build): 1 time
* `Trilinos-atdm-chama-intel-debug-openmp` (standard ATDM build): 1 time
* `Trilinos-atdm-rhel6-gnu-opt-openmp` (standard ATDM build): 2 times
* `Trilinos-atdm-waterman-cuda-9.2-debug` (standard ATDM build): 1 time
In each of these 10 failures in the last 3 months, such as the CI failure today shown [here](https://testing.sandia.gov/cdash-dev-view/testDetails.php?test=56264374&build=4031303), it shows failures like:
```
projectAndNormalizeGen() returned rank 5
|| <S,S> - I || after : 2.65912e-11
1|| S_in - X1*C1 - X2*C2 - S_out*B || : 1.70776e-09
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv tolerance exceeded! test failed!
```
The location of these failures seems to change in this test but all of the failures appear to be "tolerance exceeded! test failed!"
Is there some type of non-deterministic behavior in this test or in the underlying Anasazi code that allows for these types of random failures?
## Steps to Reproduce
Given that this test seems to be failing randomly only very occasionally, this might be hard to reproduce locally. But given that this has failed in the post-push GCC 4.8.4 CI build and the GCC 4.9.3 PR build one might be able to use one of those.
Keep promoted "ATDM" builds of Trilinos cleanhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3523install gitdist with trilinos install2018-09-27T17:02:35ZJames Willenbringinstall gitdist with trilinos install*Created by: rppawlo*
Is there any way we can get gitdist installed into the bin directory during trilinos installs? Might need a configure flag to enable/disable this capability?
@bartlettroscoe
@bathmatt *Created by: rppawlo*
Is there any way we can get gitdist installed into the bin directory during trilinos installs? Might need a configure flag to enable/disable this capability?
@bartlettroscoe
@bathmatt https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3515Framework: POSIX compatibility of build scripts2018-09-26T22:37:23ZJames WillenbringFramework: POSIX compatibility of build scripts*Created by: cgcgcg*
@trilinos/framework
## Expectations
It would be nice if the build scripts would work on all shells, and not just on bash. Examples of things that seem to create trouble are comparisons with `==` instead of `=` ...*Created by: cgcgcg*
@trilinos/framework
## Expectations
It would be nice if the build scripts would work on all shells, and not just on bash. Examples of things that seem to create trouble are comparisons with `==` instead of `=` and usage of the variable `BASH_SOURCE`.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3469Configuration of CUDA-enabled build fails2019-04-18T18:03:54ZJames WillenbringConfiguration of CUDA-enabled build fails*Created by: pelesh*
Configuration of a CUDA-enabled Tpetra/Kokkos build fails at the point where CMake checks for C++ compiler. The error message is:
```
Linking CXX executable cmTC_babeb
/usr/tce/packages/cmake/cmake-3.5.2/bi...*Created by: pelesh*
Configuration of a CUDA-enabled Tpetra/Kokkos build fails at the point where CMake checks for C++ compiler. The error message is:
```
Linking CXX executable cmTC_babeb
/usr/tce/packages/cmake/cmake-3.5.2/bin/cmake -E cmake_link_script
CMakeFiles/cmTC_babeb.dir/link.txt --verbose=1
/usr/tce/packages/openmpi/openmpi-2.0.0-gcc-6.1.0/bin/mpicxx
CMakeFiles/cmTC_babeb.dir/testCXXCompiler.cxx.o -o cmTC_babeb -rdynamic
nvcc fatal : Unknown option 'rdynamic,-fexceptions,-pthread'
gmake[1]: *** [cmTC_babeb] Error 1
```
It seems as if Kokkos' `nvc_wrapper` does not insert `-Xlinker` flags correctly.
I am building from current master branch on a system with following configuration:
```
$ module list
Currently Loaded Modules:
1) StdEnv 2) gcc/6.1.0 3) cuda/9.1.85 4) openmpi/2.0.0 5) cmake/3.5.2
```
The same issue occurs with different openmpi, CUDA, CMake and gcc versions.
I am following Tpetra build instructions from `$Trilinos/packages/tpetra/doc/FAQ.txt`, and I set environment variables like this:
```
export OMPI_CXX=${Trilinos}/packages/kokkos/bin/nvcc_wrapper
export CUDA_LAUNCH_BLOCKING=1
export CUDA_MANAGED_FORCE_DEVICE_ALLOC=1
```
I use following configuration script to set cmake options:
```
#!/bin/bash
cmake \
-D CMAKE_C_COMPILER="mpicc" \
-D CMAKE_CXX_COMPILER="mpicxx" \
-D CMAKE_Fortran_COMPILER="mpif90" \
\
-D Trilinos_CXX11_FLAGS="-std=c++11 --expt-extended-lambda" \
\
-D Trilinos_ENABLE_OpenMP=OFF \
-D TPL_ENABLE_Pthread=OFF \
\
-D Trilinos_ENABLE_Teuchos=ON \
-D Trilinos_ENABLE_Tpetra=ON \
-D Tpetra_INST_SERIAL=ON \
-D Tpetra_INST_OPENMP=OFF \
\
-D Trilinos_ENABLE_Kokkos=ON \
-D Trilinos_ENABLE_KokkosCore=ON \
-D Kokkos_ENABLE_Serial=ON \
-D Kokkos_ENABLE_OpenMP=OFF \
-D Kokkos_ENABLE_Pthread=OFF \
-D Kokkos_ENABLE_Cuda=ON \
-D Kokkos_ENABLE_Cuda_UVM=ON \
-D Kokkos_ENABLE_Cuda_Lambda=ON \
-D Kokkos_ENABLE_Cuda_Relocatable_Device_Code=OFF \
-D TPL_ENABLE_CUDA=ON \
\
-D TPL_ENABLE_MPI=ON \
-D MPI_USE_COMPILER_WRAPPERS=ON \
\
-D Tpetra_INST_CUDA:BOOL=ON \
../Trilinos
```
Any advice how to get past this point would be most appreciated.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3501Framework: Windows build not posting to dashboard2018-09-29T03:06:13ZJames WillenbringFramework: Windows build not posting to dashboard*Created by: csiefer2*
Again.*Created by: csiefer2*
Again.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/3435Framework: Autotester console output unhelpful2018-09-13T17:27:05ZJames WillenbringFramework: Autotester console output unhelpful*Created by: csiefer2*
Can we make this more useful to the developer?
See this PR:
https://github.com/trilinos/Trilinos/pull/3429
We get this unhelpful output:
17) atdm-ninja_fortran/1.7.2
MPI type = sems-mpich/3.2
CDash Track...*Created by: csiefer2*
Can we make this more useful to the developer?
See this PR:
https://github.com/trilinos/Trilinos/pull/3429
We get this unhelpful output:
17) atdm-ninja_fortran/1.7.2
MPI type = sems-mpich/3.2
CDash Track = Pull Request
*** Generating set of Trilinos enables given modified packages from
*** git commit origin/develop to HEAD
TRILINOS_DIR=/scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos
TRILINOS_SCRIPTS_DIR=/scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos/cmake/std/../..
TRIBITS_DIR=/scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos/cmake/std/../../cmake/tribits
A) Generate the Trilinos Packages definition and depencencies XML file
Wrote the file 'TrilinosPackageDependencies.xml'
B) Get the set of changed files
Current directory: /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos
git diff --name-only origin/develop..HEAD > /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/changed-files.txt
Wrote file 'changed-files.txt'
Current directory: /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1
C) Get the unfiltered list of changed Trilinos packages (including 'ALL_PACKAGES')
CHANGED_PACKAGES_FULL_LIST='MueLu'
D) Filter list of changed packages to get only the PT packages
CHANGED_PACKAGES_PT_LIST='MueLu'
E) Generate the *.cmake enables file
Wrote file 'packageEnables.cmake'
Enabled packages:
-- Setting Trilinos_ENABLE_MueLu = ON
Build name = PR-3429-test-Trilinos_pullrequest_intel_17.0.1-836
Cur dir = /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/TFW_testing_single_configure_prototype
Source dir = /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos
Binary dir = /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/pull_request_test
Parallel level = 18
skip_by_parts_submit = OFF
skip_single_submit = ON
skip_update_step = ON
skip_upload_config_files = OFF
skip_clean_build_dir = OFF
Subproject count = 53
Dashboard model = Experimental
Dashboard track = Pull Request
Running configuration:
/projects/sems/install/rhel6-x86_64/atdm/binary-install/cmake-3.11.1-Linux-x86_64/bin/cmake
-C "/scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos/cmake/std/PullRequestLinuxIntelTestingSettings.cmake"
-C "/scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/packageEnables.cmake"
-DTrilinos_ENABLE_TESTS:BOOL=ON
-G "Ninja"
/scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/Trilinos
CTEST_DROP_LOCATION = /cdash/submit.php?project=Trilinos
CDash URL1 = https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&display=project&filtercount=3&showfilters=1&filtercombine=and&field1=site&compare1=61&value1=ascic158&field2=buildname&compare2=61&value2=PR-3429-test-Trilinos_pullrequest_intel_17.0.1-836&field3=buildstamp&compare3=61&value3=20180912-0916-Pull Request
CDash URL2 = https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&display=project&filtercount=2&showfilters=0&filtercombine=and&field1=buildname&compare1=61&value1=PR-3429-test-Trilinos_pullrequest_intel_17.0.1-836&field2=buildstamp&compare2=61&value2=20180912-0916-Pull Request
CDash URL3 = https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&filtercount=2&showfilters=0&filtercombine=and&field1=buildname&compare1=61&value1=PR-3429-test-Trilinos_pullrequest_intel_17.0.1-836&field2=buildstamp&compare2=61&value2=20180912-0916-Pull Request
Starting configure step.
Each . represents 1024 bytes of output
.................................................. Size: 50K
.................................................. Size: 100K
.................................... Size of output: 135K
configure submit error = 0
Configure suceeded.
Starting build step.
Each symbol represents 1024 bytes of output.
.................................................. Size: 49K
.................................................. Size: 99K
.................................................. Size: 149K
.................................................. Size: 199K
.................................................. Size: 249K
.................................................. Size: 299K
.................................................. Size: 349K
.................................................. Size: 400K
.................................................. Size: 449K
.................................................. Size: 499K
.................................................. Size: 549K
.................................................. Size: 599K
.................................................. Size: 649K
.................................................. Size: 699K
.......... Size of output: 709K
Build succeeded.
build submit error = 0
Starting testing step.
CMake Error at /scratch/trilinos/workspace/trilinos-folder/Trilinos_pullrequest_intel_17.0.1/TFW_testing_single_configure_prototype/simple_testing.cmake:193 (message):
Test failed with error -1
test submit error = 0
File upload submit error = 0
Single configure/build/test failed. The error code was: 255
Build step 'Execute shell' marked build as failure
Finished: FAILUREhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3360Trilinos PR testing needs a build with KOKKOS_ENABLE_DEPRECATED_CODE=OFF2018-08-27T17:35:56ZJames WillenbringTrilinos PR testing needs a build with KOKKOS_ENABLE_DEPRECATED_CODE=OFF*Created by: mhoemmen*
@trilinos/framework
Trilinos developers keep adding use of deprecated Kokkos functions back into Trilinos. See e.g., #3358. They do so because no PR test builds disable deprecated Kokkos functions, and becau...*Created by: mhoemmen*
@trilinos/framework
Trilinos developers keep adding use of deprecated Kokkos functions back into Trilinos. See e.g., #3358. They do so because no PR test builds disable deprecated Kokkos functions, and because Trilinos enables deprecated Kokkos functions by default. If we disable deprecated Kokkos functions in at least one PR test build, Trilinos developers will learn not to rely on those functions.
## Motivation and Context
See Sierra Ticket 19694.
## Possible Solution
In at least one PR test build, set KOKKOS_ENABLE_DEPRECATED_CODE=OFF.
## Related Issues
* Related to #3358 https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3276Trilinos auto PR tester stability issues2019-05-02T13:20:11ZJames WillenbringTrilinos auto PR tester stability issues*Created by: bartlettroscoe*
@trilinos/framework
## Description
Over the last few weeks and months, the Trilinos auto PR tester has seen several cases where one or more PR builds for a given PR testing iteration failed to produce ...*Created by: bartlettroscoe*
@trilinos/framework
## Description
Over the last few weeks and months, the Trilinos auto PR tester has seen several cases where one or more PR builds for a given PR testing iteration failed to produce results on CDash or showed build or test failures that were not related to the changes on that particular PR.
This Story is to log these fails and keep track of them in order to provide some statistics about these cases in order to inform how to address them. This should replace making comments in individual PRs that exhibit these types of problems like #3260 and #3213.
## PR Builds Showing Random Failures
Below are a few examples of the stability problems (but are not all of the problems).
| PR ID | Num PR Builds to reach passing | First test trigger | Start first test| Passing test | Merge PR |
| --: | --: | --: | --: | --: | --: |
| #3258 | 2 | [8/8/2018 2:35 PM ET](https://github.com/trilinos/Trilinos/pull/3258#issue-207098955) | [8/8/2018 2:44 PM](https://github.com/trilinos/Trilinos/pull/3258#issuecomment-411510956) | [8/8/2018 9:15 PM ET]() | Not merged |
| #3260 | 4 | [8/8/2018 5:22 PM ET](https://github.com/trilinos/Trilinos/pull/3260#issue-207141537) | [8/8/2018 6:31 PM ET](https://github.com/trilinos/Trilinos/pull/3260#issuecomment-411574370) | [8/10/2018 4:13 AM ET](https://github.com/trilinos/Trilinos/pull/3260#issuecomment-412010497) | [8/10/2018 8:25 AM](https://github.com/trilinos/Trilinos/pull/3260#event-1782381644) |
| #3213 | 3 | [7/31/2018 4:30 PM ET](https://github.com/trilinos/Trilinos/pull/3213#issue-205233060) | [7/31/2018 4:57 PM ET](https://github.com/trilinos/Trilinos/pull/3213#issuecomment-409365522) | [8/1/2018 9:48 AM ET](https://github.com/trilinos/Trilinos/pull/3213#issuecomment-409580677) | [8/1/2018 9:53 AM ET](https://github.com/trilinos/Trilinos/pull/3213#event-1765281809) |
| #3098 | 4 | [7/12/2018 12:52 PM ET](https://github.com/trilinos/Trilinos/pull/3098#issue-201063953) | [7/12/2018 1:07 PM ET](https://github.com/trilinos/Trilinos/pull/3098#issuecomment-404582631) | [7/13/2018 11:12 PM ET](https://github.com/trilinos/Trilinos/pull/3098#issuecomment-404994581) | [7/14/2018 10:59 PM ET](https://github.com/trilinos/Trilinos/pull/3098#event-1733896640) |
| #3369 | 6 | [8/29/2018 9:08 AM ET](https://github.com/trilinos/Trilinos/pull/3369#issue-211746901) | [8/29/2018 9:16 AM ET](https://github.com/trilinos/Trilinos/pull/3369#issuecomment-416948915) | [8/31/2018 6:09 AM ET](https://github.com/trilinos/Trilinos/pull/3369#issuecomment-417618824) | [8/31/2018 8:33 AM ET](https://github.com/trilinos/Trilinos/pull/3369#event-1820478271) |
Improve productivity, stability, and quality of Trilinoshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/3272package_subproject_list.cmake static in Trilinos PR tester?2018-08-09T19:58:47ZJames Willenbringpackage_subproject_list.cmake static in Trilinos PR tester?*Created by: bartlettroscoe*
@trilinos/framework,
Is the file package_subproject_list.cmake used at:
https://github.com/trilinos/Trilinos/blob/0df591fd6d9b9ccd91bd2695cc22665aa468886d/cmake/std/PullRequestLinuxDriver.sh#L206
st...*Created by: bartlettroscoe*
@trilinos/framework,
Is the file package_subproject_list.cmake used at:
https://github.com/trilinos/Trilinos/blob/0df591fd6d9b9ccd91bd2695cc22665aa468886d/cmake/std/PullRequestLinuxDriver.sh#L206
statically generated and require manual updating? If so, that would explain why the PR builds are not testing the new PT package TrilinosFrameworkTests.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/3263Test ShyLU_NodeTacho_Tacho_TestSerial_double_MPI_1 randomly failing in CI and...2018-08-09T19:59:42ZJames WillenbringTest ShyLU_NodeTacho_Tacho_TestSerial_double_MPI_1 randomly failing in CI and PR GCC 4.8.4 + OpenMP builds*Created by: bartlettroscoe*
@trilinos/shylu, @trilinos/framework, @srajama1 (Trilinos Linear Solvers Product Lead)
## Expectations
A test should not fail unless a changes is made to break it. A test should not randomly fail.
...*Created by: bartlettroscoe*
@trilinos/shylu, @trilinos/framework, @srajama1 (Trilinos Linear Solvers Product Lead)
## Expectations
A test should not fail unless a changes is made to break it. A test should not randomly fail.
## Current Behavior
Looking at the four most recent failures of the test `ShyLU_NodeTacho_Tacho_TestSerial_double_MPI_1` in [this query](https://testing-vm.sandia.gov/cdash/queryTests.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=4&showfilters=1&filtercombine=and&field1=testname&compare1=61&value1=ShyLU_NodeTacho_Tacho_TestSerial_double_MPI_1&field2=status&compare2=62&value2=passed&field3=status&compare3=62&value3=notrun&field4=buildstarttime&compare4=84&value4=now) the test appears to be randomly failing in the GCC 4.8.4 OpenMPI builds. In the most recent case, this test broke the auto PR GCC 4.8.4 + OpenMP build in PR #3260. IN each of the last for failures of this test dating back to 6/28/2018, they all fail showing:
```
....
[ RUN ] CrsMatrixBase.matrixmarket
unknown file: Failure
C++ exception with description "View bounds error of view ap ( 13 < 13 )
Traceback functionality not available
" thrown in the test body.
[ FAILED ] CrsMatrixBase.matrixmarket (23 ms)
...
[ FAILED ] 1 test, listed below:
[ FAILED ] CrsMatrixBase.matrixmarket
1 FAILED TEST
```
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
## Motivation and Context
<!---
How has this expectation failure affected you? What are you trying to
accomplish? Why do we need to address this? What does it have to do with
anything? Providing context helps us come up with a solution that is most
useful in the real world.
-->
## Definition of Done
The test `ShyLU_NodeTacho_Tacho_TestSerial_double_MPI_1` is fixed to make it so that it does not randomly fail or is removed for CI and auto PR testing.
## Possible Solution
Fix it so that it does not randomly fail or remove it from CI and auto PR testing.
## Steps to Reproduce
See https://github.com/trilinos/Trilinos/wiki/Reproducing-PR-Testing-Errors.
## Your Environment
Standard SEMS GCC 4.8.4 auto PR build env (see above).