Skip to content

Add 'release-debug' build type (#3633) and change some 'waterman' builds (#3336)

James Willenbring requested to merge bartlettroscoe:3633-atdm-release-debug into develop

Created by: bartlettroscoe

CC: @fryeguy52

Description

This will allow many of the ATDM Trilinos 'debug' builds to be switched to 'release-debug' builds and help to avoid a bunch of timeouts that we are dealing with.

Switch some 'waterman' 'debug' builds to new 'release-debug' builds (#3633 (closed))

I kept the existing cuda-9.2-debug-Power9-Volta70 build since there are currently not any timing out tests in that build and I figured that the CUDA build was most likey the one a developer would want to run with a debugger. But I created a new cuda-9.2-release-debug-Power9-Volta70 build so that we can avoid having to disable slow Kokkos, KokkosKernels, and other tests that run super slow with -O0.

I changed the build gnu-debug-openmp-Power9-Volta70 to a gnu-release-debug-openmp-Power9-Volta70 build since I don't think it is as important to run this build with a debugger and the full 'debug' build and this build currently has some timing-out tests for Kokkos and KokkosKernals as described in #3336 (closed). (The new gnu-release-debug-openmp-Power9-Volta70 build has not have any timeouts.) If the APP teams tell us they want a full gnu-debug-openmp-Power9-Volta70 build, then we will add one back and deal with the timeouts.

NOTE: By having both 'debug' and 'release-debug' builds, we can be free to disable some slow tests in the full 'debug' build and not loose much runtime debug checking since these tests will be running in the 'release-debug' build (with runtime debug checking enabled). So going forward, if a test times-out in the 'debug' build but not the 'release-debug' build, then we will just disable it in the 'debug' build and move on.

I also renamed the 'cuda' builds to 'cuda-9.2' builds since that is what they are and that matches the Jenkins drive names.

Motivation and Context

We want to avoid timeouts like #3336 (closed) recently and going forward (see #3633 (closed)).

How Has This Been Tested?

I tested this on on 'waterman' with:

$ bsub -x -Is -n 20 \
  ./checkin-test-atdm.sh all --enable-packages=Kokkos,KokkosKernels --local-do-all

and it returned:

PASSED (NOT READY TO PUSH): Trilinos: waterman3

Wed Oct 17 12:41:58 MDT 2018

Enabled Packages: Kokkos, KokkosKernels

Build test results:
-------------------
0) MPI_RELEASE_DEBUG_SHARED_PT_OPENMP => Test case MPI_RELEASE_DEBUG_SHARED_PT_OPENMP was not run! => Does not affect push readiness! (-1.00 min)
1) gnu-release-debug-openmp-Power9-Volta70 => passed: passed=35,notpassed=0 (3.52 min)
2) gnu-opt-openmp-Power9-Volta70 => passed: passed=35,notpassed=0 (3.34 min)
3) cuda-9.2-release-debug-Power9-Volta70 => passed: passed=35,notpassed=0 (11.84 min)
4) cuda-9.2-debug-Power9-Volta70 => passed: passed=35,notpassed=0 (9.35 min)
5) cuda-9.2-opt-Power9-Volta70 => passed: passed=35,notpassed=0 (3.69 min)

A current successful pull does *not* exist => Not ready for final push!

Explanation: In order to safely push, the local working directory needs
to be up-to-date with the global repo or a full integration has not been
performed!


REQUESTED ACTIONS: PASSED

NOTE: The timing-out tests KokkosContainers_UnitTest_Serial_MPI_1 and KokkosKernels_graph_serial_MPI_1 for the updated build gnu-release-debug-openmp-Power9-Volta70 (which used to be the full debug build gnu-debug-openmp-Power9-Volta70) reported in #3336 (closed) are gone! For the build gnu-release-debug-openmp-Power9-Volta70 the ctest output showed:

30/35 Test #34: KokkosKernels_graph_serial_MPI_1 .................   Passed   48.19 sec
...
35/35 Test #25: KokkosContainers_UnitTest_Serial_MPI_1 ...........   Passed  105.93 sec

So merging this branch will fix #3336 (closed).

Checklist

  • My commit messages mention the appropriate GitHub issue numbers.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Merge request reports