Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2018-12-20T15:56:10Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/4069Framework: Intel Autotester is Woofing2018-12-20T15:56:10ZJames WillenbringFramework: Intel Autotester is Woofing*Created by: csiefer2*
Status Flag 'Pull Request AutoTester' - Failure: Timed out waiting for job Trilinos_pullrequest_intel_17.0.1 to start: Total Wait = 603
Other jobs have been previously started - We must stop them...
*Created by: csiefer2*
Status Flag 'Pull Request AutoTester' - Failure: Timed out waiting for job Trilinos_pullrequest_intel_17.0.1 to start: Total Wait = 603
Other jobs have been previously started - We must stop them...
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4424Framework: Parameterize CDash Tracks for Pull Request Tests2019-02-25T17:11:05ZJames WillenbringFramework: Parameterize CDash Tracks for Pull Request Tests*Created by: william76*
@trilinos/framework
We discussed parameterizing the PR testing drivers so we can specify in the Jenkins job which track we'd like the tests to go to.
I'm testing this [on my fork][1], but I added a parameter...*Created by: william76*
@trilinos/framework
We discussed parameterizing the PR testing drivers so we can specify in the Jenkins job which track we'd like the tests to go to.
I'm testing this [on my fork][1], but I added a parameter `PULLREQUEST_CDASH_TRACK` which, if set and non-empty will set the `CDASH_TRACK` variable that's used inside the `PullRequestLinuxDriver-Test.sh` script.
I'm running a quick test using my jenkins simulator and it looks like it's working as intended... using '0000' as the PR number, it's showing up in the Clean track [here][2].
### Tasks
- [x] Update `PullRequestLinuxDriver-Test.sh` to take in a parameter for the desired CDash track to report results to.
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_cuda_9.2][3]
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_gcc_4.8.4][4]
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_gcc_4.9.3][5]
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_gcc_4.9.3_SERIAL][6]
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_gcc_7.2.0][7]
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_gcc_7.3.0][8]
- [x] Add parameter `PULLREQUEST_CDASH_TRACK` to [Trilinos_pullrequest_intel_17.0.1][9]
- [x] Update PR Driver configuration in the autotester.
FYI: @jwillenbring
[1]: https://github.com/william76/Trilinos/blob/parameterized-pr-cdash-track/cmake/std/PullRequestLinuxDriver-Test.sh#L298-L312
[2]: https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=2&showfilters=1&filtercombine=and&field1=buildname&compare1=63&value1=PR-0000-test&field2=buildstarttime&compare2=84&value2=NOW
[3]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_cuda_9.2/
[4]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_gcc_4.8.4/
[5]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_gcc_4.9.3/
[6]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_gcc_4.9.3_SERIAL/
[7]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_gcc_7.2.0/
[8]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_gcc_7.3.0/
[9]: https://ascic-jenkins.sandia.gov/job/trilinos-folder/job/Trilinos_pullrequest_intel_17.0.1/
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4537Amesos2 does not compile with UMFPACK, SuperLU, complex double, and eti=off2019-03-07T21:17:35ZJames WillenbringAmesos2 does not compile with UMFPACK, SuperLU, complex double, and eti=off*Created by: prwolfe*
Basically the compiler cannot chose from 2 convert functions, but does fine the ETI is on as the instantiation gets only one at a time.
@trilinos/amesos2
## Expectations
Amesos2 should build either with or ...*Created by: prwolfe*
Basically the compiler cannot chose from 2 convert functions, but does fine the ETI is on as the instantiation gets only one at a time.
@trilinos/amesos2
## Expectations
Amesos2 should build either with or without ETI on
## Current Behavior
A build matching https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&parentid=4650329 but with ETI=off will fail to compile Amesos2_Details_registerLinearSolverFactory.cpp.o because it cannot pick between
packages/amesos2/src/Amesos2_Umfpack_TypeMap.hpp:98:7: error: candidates are: class Teuchos::ValueTypeConversionTraits<TypeTo, std::complex<double> >
class ValueTypeConversionTraits<TypeTo, std::complex<double>>
and
Trilinos/packages/amesos2/src/Amesos2_Superlu_TypeMap.hpp:192:7: error: class Teuchos::ValueTypeConversionTraits<SLU::Z::doublecomplex, TypeFrom>
class ValueTypeConversionTraits<SLU::Z::doublecomplex, TypeFrom>
These take opposite approaches, but can both fulfill the request.
## Motivation and Context
This was found when checking a trilinos build against Sierra. Customers should be able to build either with or without ETI or one options should be disabled.
I am tagging framework as we need to make sure we have a t least one build that covers this at some level (we currently do all builds with ETI=on as far as I can tell.)
## Definition of Done
Amesos2 compiles both with and without ETI and the requested packages available.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4600Teuchos: Some CMake checks happen at run time unconditionally; this hinders c...2019-03-19T15:14:17ZJames WillenbringTeuchos: Some CMake checks happen at run time unconditionally; this hinders cross compilation*Created by: mhoemmen*
@trilinos/teuchos @trilinos/framework @theguruat12 @vbrunini @rrdrake
@theguruat12 and I found that `teuchos/CMakeLists.txt` does some checks that involve running code. That's normally OK, except that it's no...*Created by: mhoemmen*
@trilinos/teuchos @trilinos/framework @theguruat12 @vbrunini @rrdrake
@theguruat12 and I found that `teuchos/CMakeLists.txt` does some checks that involve running code. That's normally OK, except that it's not OK for cross compilation. For example, when building KNL-specific binaries on a login node that's not KNL, a lot of tests (like `HAVE_TEUCHOS_BLASFLOAT`) will incorrectly report back false. This will break the build if `Scalar=float` is enabled, which @vbrunini needs.
@theguruat12 and I have prototyped a fix that seems to work. It follows the preexisting Trilinos idiom of letting users set CMake options in advance, if they want to avoid CMake tests that run code. I will submit a PR soon that implements this fix.https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4614PR test timeouts preventing PRs from passing2019-03-18T23:29:57ZJames WillenbringPR test timeouts preventing PRs from passing*Created by: ndellingwood*
@trilinos/framework
The following test timeouts have resulted in several PRs failing and requiring re-test:
```
PanzerAdaptersSTK_PoissonInterfaceExample_2d_diffsideids_MPI_1
ROL_example_PDE-OPT_0ld_ad...*Created by: ndellingwood*
@trilinos/framework
The following test timeouts have resulted in several PRs failing and requiring re-test:
```
PanzerAdaptersSTK_PoissonInterfaceExample_2d_diffsideids_MPI_1
ROL_example_PDE-OPT_0ld_adv-diff-react_example_02_MPI_4
ROL_example_PDE-OPT_navier-stokes_example_01_MPI_4
```
Of immediate consequence is that this is preventing PR #4608 from completing and merging in, which will result in any Cuda PR testing that involves Ifpack2 from passing.
The tests timing out above, along with #4608 in some cases which is also unable to complete PR testing due to these tests timing out is preventing PR completion of PRs #4609, #4603, #4604, #4601, #4597, ...https://gitlab.osti.gov/jmwille/Trilinos/-/issues/4809Framework: Non-framework machines no longer able to report to Cdash2019-04-09T23:16:48ZJames WillenbringFramework: Non-framework machines no longer able to report to Cdash*Created by: csiefer2*
And for that matter, the entire Nightly track is gone. SAD!
(Originally noticed by @lucbv)
@trilinos/framework
@trilinos/tpetra This will impact deprecation work after the release if it is not resolved...*Created by: csiefer2*
And for that matter, the entire Nightly track is gone. SAD!
(Originally noticed by @lucbv)
@trilinos/framework
@trilinos/tpetra This will impact deprecation work after the release if it is not resolved by then.