-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to new devpack/20180521/openmpi/2.1.2/gcc/7.2.0/cuda/9.2.88 env on 'white' and 'ride' (#3290) #3549
Switch to new devpack/20180521/openmpi/2.1.2/gcc/7.2.0/cuda/9.2.88 env on 'white' and 'ride' (#3290) #3549
Conversation
trilinos#3290) This new env also has the correct netcdf build for SEACAS (see trilinos#3288).
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
Status Flag 'Pull Request AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 2 Hrs 30 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 1009 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3 # 1768 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 1463 (click to expand)
|
@trilinos/framework, Looks like the auto tester failed above due to not being able to submit results to CDash for the GCC 4.8.4 build showing the error:
Can the CTest -S driver turn on the CTest feature for doing multiple retries? The TriBITS CTest -S driver has been doing that for nearly 10 years (and Kitware implemented that feature because of us and our contract with Kitware years ago). |
Status Flag 'Pull Request AutoTester' - User Requested Retest - Label AT: RETEST will be reset after testing. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
Status Flag 'Pull Request AutoTester' - User Requested Retest - Label AT: RETEST will be reset after testing. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand)Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - - This Pull Request Requires Inspection... The code must be inspected by a member of the Team before Testing/Merging |
All Jobs Finished; status = PASSED, However Inspection must be performed before merge can occur... |
@fryeguy52 or @mhoemmen, if you are online and can see this, can I get a quick approval for this PR? |
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ fryeguy52 ]! |
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
Merge on Pull Request# 3549: IS A SUCCESS - Pull Request successfully merged |
CC: @trilinos/seacas, @fryeguy52
Description
This changes to use a new consistent GCC 7.2.0 + OpenMPI 2.1.2 + CUDA 9.2 + TPLs env on 'white' and 'ride'. Before this, on 'white' we were using OpenMPI 2.1.2 to compile and link libraries and execuables in Trilinos but were linking against TPLs built with OpenMPI 3.1.0 (see #3290). This new set of modules uses OpenMPI 2.1.2 for the TPLs as well to create a 100% consistent env.
@nmhamster noted that he had to reduce the compiler optimization level of HDF5 from
-O3
to-O2
or you get a could SEACAS tests that fail, as described in #3288. (So the problem in #3288 was not the NetCDF configuration but was the HDF5 compiler options).Motivation and Context
It was not good to be using a mixture of OpenMPI 2.1.2 and OpenMPI 3.1.0 on 'white'. And we need to use OpenMPI 2.1.2 to avoid problems with MPI handling of CUDA memory impacting Ifpack2 (see #3290). Also, we need the TPLs built so that the SEACAS tests pass as described above and in #3288.
How Has This Been Tested?
I tested this on 'white' by running:
That gave the test results ...
gnu-opt-openmp-Power8:
cuda-9.2-opt-Power8-Kepler37:
Note that we don't run run Zoltan or Pliris tests as part of the current ATDM Trilinos builds. I just use
--enable-all-packages=on
as a shortcut. (I will set up the ATDM Trilinos build to automatically disable tests in the non-tested packages so that we can use this shortcut in the future).As for the timing out KokkosCore and Panzer tests, I ran them by by themselves and they both passed just fine as shown with:
We know that these tests run on top of each other and all run on the same GPU so increased runtimes are expected. Hopefully the nightly drivers will not show any timeouts. If they do, we will deal with them.
Checklist