Add kunpeng2 configuration for release 3.23

3.23/bioc/kunpeng2/config.sh

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+# ===================================
+# Settings for kunpeng2 (Linux ARM64)
+# ===================================
+
+
+
+#set -x  # print commands and their arguments as they are executed
+
+export BBS_DEBUG="0"
+
+export BBS_NODE_HOSTNAME="kunpeng2"
+export BBS_USER="biocbuild"
+export BBS_WORK_TOPDIR="/home/biocbuild/bbs-3.23-bioc"
+export BBS_R_HOME="/home/biocbuild/R/R"
+export R_LIBS="$BBS_R_HOME/site-library"
+
+# kunpeng2 has 32 logical CPUs.
+export BBS_NB_CPU=25
+export BBS_BUILD_NB_CPU=16
+export BBS_CHECK_NB_CPU=22
+export BBS_EXTRA_CHECK_OPTIONS="--no-vignettes"
+
+# Central build node is bbscentral2 on Jetstream2.
+export BBS_CENTRAL_ROOT_URL="http://149.165.171.124"
+export BBS_PRODUCT_TRANSMISSION_MODE="none"
+
+# Source tarballs produced during STAGE3 won't be propagated
+# so we don't need to push them to the central builder.
+export DONT_PUSH_SRCPKGS="1"
+
+
+
+# Shared settings (by all Unix nodes).
+
+wd0=$(pwd)
+cd ..
+. ./config.sh
+cd "$wd0"

3.23/bioc/kunpeng2/run.sh

@@ -0,0 +1,12 @@
+#!/bin/bash
+
+. ./config.sh
+
+. $BBS_HOME/utils/clean-before-run.sh
+
+$BBS_PYTHON_CMD $BBS_HOME/BBS-run.py no-bin
+
+# We have to use brute force because some R processes might still be running
+# in the background. This will kick out the user BBS is running as!
+sleep 60  # wait 1 min before the kill
+kill -9 -1