We use gitlab-runner in conjunction with reframe. On the target machines we have gitlab-runner instances perpetually running in user mode on login nodes with nohup.
This is a weird one:
from within durham network, ssh to ncc1.clients.dur.ac.uk in ncc start screen session and from there ssh into hamilton and then do /ddn/data/gcgt96/bin/gitlab-runner run
this is the toml file /ddn/home/gcgt96/.gitlab-runner/config.toml
/cosma5/data/durham/hschulz$ nohup ./bin/gitlab-runner run &
toml bin/gitlab-runner pip instsall GitPython touch
DINE | HAMILTON | BEDE | COSMA |
---|---|---|---|
y | y | 22.6. | n |
nohup /var/local/gitlab-runner/gitlab-runner run & | nohup /ddn/data/gcgt96/bin/gitlab-runner run & |
module purge
module load python/3.6.5
pip3 install --user keras-preprocessing==1.0.1
git clone https://github.com/eth-cscs/reframe.git
cd reframe
./bootstrap.sh
./bin/reframe -V
Note: Markโs reframe scripts expects the repo to be in $HOME/Peano
git clone git@gitlab.lrz.de:hpcsoftware/Peano.git --branch p4 --single-branch --depth=1