From ca30847913efd1641dc76c3ec4fab39af590804a Mon Sep 17 00:00:00 2001
From: G-Ragghianti <ragghianti@icl.utk.edu>
Date: Fri, 14 Mar 2025 14:00:11 -0400
Subject: [PATCH] Converting CI to use pre-built spack environment

---
 .github/CI/github_runner.yaml | 22 ----------
 .github/CI/spack_setup.sh     | 80 +----------------------------------
 2 files changed, 2 insertions(+), 100 deletions(-)
 delete mode 100644 .github/CI/github_runner.yaml

diff --git a/.github/CI/github_runner.yaml b/.github/CI/github_runner.yaml
deleted file mode 100644
index dbc7c069..00000000
--- a/.github/CI/github_runner.yaml
+++ /dev/null
@@ -1,22 +0,0 @@
-spack:
-  definitions:
-  - pkgs:
-    - gcc@12
-    - git
-    - patch
-    - flex
-    - bison
-    - hwloc
-    - python@3
-    - py-cython
-    - cmake
-    - ninja
-    - otf2@2.3
-    - openmpi
-    - openblas
-    - scalapack
-
-  view: true
-  specs:
-    - matrix:
-      - [$pkgs]
diff --git a/.github/CI/spack_setup.sh b/.github/CI/spack_setup.sh
index 310c3d8b..4dcd975f 100644
--- a/.github/CI/spack_setup.sh
+++ b/.github/CI/spack_setup.sh
@@ -1,83 +1,7 @@
 # This file should be "sourced" into your environment
 # to set up the spack repository
 
-SPACK_DIR=${HOME}/spack
 
-sload () {
-  # Installs a software package and loads it into the environment
-  spack install --reuse --fail-fast $@
-  spack load --first $@
-}
-
-slocation () {
-  # Returns the installation directory of a given software package
-  HASH=`spack find --no-groups --loaded -l $@ | head -1 | awk '{print $1}'`
-  spack location -i /$HASH
-}
-
-# Only do the heavy lifting once per github_action invocation
-if [ ${GITHUB_ACTION} != "setup" ]; then
-  echo "::group::Loading spack ${RUNNER_ENV} env"
-  source $SPACK_DIR/share/spack/setup-env.sh
-  spack env activate ${RUNNER_ENV}
-  echo "::endgroup::"
-  return
-fi
-
-save_dir=`pwd`
-#
-# Only update the spack clone once a day
-#
-echo "::group::Spack environment setup"
-if [ -r ${SPACK_DIR}/.git/FETCH_HEAD ]; then
-  # We should never allow spack to update it's packages, it increases the
-  # opportunity for mishandling of the runner environment. Instead, when
-  # there is a need for update, the entire runner should be flushed, such
-  # that a fresh spack install is created.
-  last_update=`stat -c %Y ${SPACK_DIR}/.git/FETCH_HEAD`
-  current=`date -d now "+%s"`
-  echo "spack is $(((current - last_update) / 86400)) days old"
-  # if [ $(((current - last_update) / 86400)) -gt 1 ]; then
-  #   echo "Last update ${last_update}, current ${current}: Do git pull spack"
-  #   cd $SPACK_DIR && git pull
-  # else
-  #   echo "git pull was less than one day ago"
-  # fi
-else
-  echo "git clone spack"
-  git clone https://github.com/spack/spack $SPACK_DIR || true
-  # We do a git pull to create the .git/FETCH_HEAD for the check
-  # next time the script is executed.
-  cd $SPACK_DIR && git pull && git status
-fi
-
-rm -rf ${HOME}/.spack
-
-echo "Load spack environment"
-source $SPACK_DIR/share/spack/setup-env.sh
-
-spack compiler find
-
-# Start with a fresh env every time
-spack env remove -y ${RUNNER_ENV} || true
-
-cd ${save_dir}
-mkdir ${RUNNER_ENV} || true
-
-# Show the known envs
-if spack env activate "${RUNNER_ENV}"; then
-  if diff ${GITHUB_WORKSPACE}/.github/CI/${RUNNER_ENV}.yaml ${SPACK_DIR}/var/spack/environments/${RUNNER_ENV}/spack.yaml > /dev/null; then
-    echo "Update spack env ${RUNNER_ENV}"
-    cp ${GITHUB_WORKSPACE}/.github/CI/${RUNNER_ENV}.yaml ${SPACK_DIR}/var/spack/environments/${RUNNER_ENV}/spack.yaml
-  fi
-  spack env update ${RUNNER_ENV}
-else
-  echo "Create spack env ${RUNNER_ENV}"
-  spack env create ${RUNNER_ENV} ${GITHUB_WORKSPACE}/.github/CI/${RUNNER_ENV}.yaml
-fi
-spack env activate ${RUNNER_ENV}
-spack concretize --force
-spack install --reuse
-
-echo "::endgroup::"
+source $SPACK_SETUP
+spack env activate dplasma