Did CMake 3.10.0 requirement break the check-in test script? (#3628) · Issues · James Willenbring / Trilinos

Did 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-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.