Add Rocky build automation via PNNL GitLab

[jacksavage]

• updates install_gridpack_deps.sh and install_gridpack.sh.
• adds definition for a gitlab build pipeline via .gitlab-ci.yml. this contains jobs that install gridpack and run gridpack tests. there is a third job that builds a container image used as the environment for those jobs.
• adds dockerfile, defining the container image.

[abhyshr]

@jacksavage : What is the status of this work?

[jacksavage]

@jacksavage : What is the status of this work?

hi @abhyshr, I was able to get the ubuntu build working and the tests are able to run (as of 31d1fb2). a few tests are failing, maybe the ones that are expected to.

right now, I'm trying to get the rocky linux (RHEL-like) build to work. I ran into an issue with the PNNL proxy and needed to request a url for the package repo list be unblocked. now I'm troubleshooting an issue with the Global Arrays install - "Could not determine the C compiler wrapped by MPI".

[jacksavage]

@wperkins, thanks for the help in regard to loading the module for mpi4py. on the rocky linux build, I'm now running into in error with the gridpack installation when running

cmake \
  -D GA_DIR:STRING=/gridpack-dependencies/ga/install_for_gridpack \
  -D BOOST_ROOT:STRING=/gridpack-dependencies/boost/install_for_gridpack \
  -D Boost_DIR:STRING=/gridpack-dependencies/boost/install_for_gridpack/lib/cmake/Boost \
  -D Boost_LIBRARIES:STRING=/gridpack-dependencies/boost/install_for_gridpack/lib \
  -D Boost_INCLUDE_DIRS:STRING=/gridpack-dependencies/boost/install_for_gridpack/include \
  -D PETSC_DIR:PATH=/gridpack-dependencies/petsc/install_for_gridpack \
  -D MPI_CXX_COMPILER:STRING=mpicxx \
  -D MPI_C_COMPILER:STRING=mpicc \
  -D MPIEXEC:STRING=mpiexec \
  -D GRIDPACK_TEST_TIMEOUT:STRING=30 \
  -D CMAKE_INSTALL_PREFIX:PATH=/build/src/install \
  -D CMAKE_BUILD_TYPE:STRING=Debug \
  -D BUILD_SHARED_LIBS=YES \
  -D Boost_NO_SYSTEM_PATHS:BOOL=TRUE \
  -D Boost_NO_BOOST_CMAKE:BOOL=TRUE \
  -D MPIEXEC_MAX_NUMPROCS:STRING=2 \
  ..

the error is

CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Boost (missing: mpi) (found suitable version "1.78.0",
  minimum required is "1.53")
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake/Modules/FindBoost.cmake:2344 (find_package_handle_standard_args)
  CMakeLists.txt:270 (find_package)

any ideas about this?

[wperkins]

[...]

CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Boost (missing: mpi) (found suitable version "1.78.0",
  minimum required is "1.53")
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake/Modules/FindBoost.cmake:2344 (find_package_handle_standard_args)
  CMakeLists.txt:270 (find_package)

any ideas about this?

Are you using the system boost package? If so, did you install the boost-openmpi package (https://rockylinux.pkgs.org/8/rockylinux-powertools-x86_64/boost-openmpi-1.66.0-13.el8.x86_64.rpm.html)?

If you are building Boost from source, do not install any system Boost packages, or add -D Boost_NO_SYSTEM_PATHS=TRUE to GridPACK configuration.

[wperkins]

hi @abhyshr, I was able to get the ubuntu build working and the tests are able to run (as of 31d1fb2). a few tests are failing, maybe the ones that are expected to.

@jacksavage, it looks like the tests that fail (wind DSA) are just timing out. You can increase the time out time with the GridPACK configuration option -D GRIDPACK_TEST_TIMEOUT (in seconds). Or, if they take more time that you can stand, you might just exclude them (ctest -E 'wind.*dsa').

Just out of curiosity, are we going to keep hiding the CI test results on PNNL's Gitlab, or is there a plan to expose the results/logs on Github?

[jacksavage]

@wperkins, looks like I was able to get all tests passing with a 120 second timeout. thanks.

in regard to exposing test results to GitHub, I haven't come across a simple way to do that. the only thing that seems to be supported by the GitLab integration is reporting the build status and providing a link to results. did we choose to build on PNNL GitLab for the eventual access to HPC? if not, I suppose moving the build to GitHub would be worth exploring - if we want results here and public.

[jacksavage]

Closing this PR because #195 contains everything needed to continue work adding Rocky Linux support.