Skip to content

Latest commit

 

History

History
299 lines (226 loc) · 11 KB

Testing.md

File metadata and controls

299 lines (226 loc) · 11 KB
Raw

I. CI Testing

Testing for pull requests is performed using github actions CI: open pull request with your changes and it will be automatically tested. For details, see build.yml, unit-test.yml and test-suite.yml and others. Cuda tests are only built but not launched in github actions CI, in other cases github actions CI is enough for release testing. For arm, arm64, riscv64, ppc64el testing is done under qemu.

II. Manual Testing

fdtd3d tests consists of three parts:

  • tests of build
  • unit tests
  • functional tests from test suite

1. Tests of build

./Tools/test-build.sh script is used to test builds with different flags.

Note: some combinations like Cuda debug builds for all solver dim modes might take hours to complete, thus, they are explicitly forbidden in cmake config.

2. Unit tests

  • ./Tools/test-units.sh script is used to run unit tests

  • ./Tools/test-units-mpi.sh script is used to run unit tests with mpi

  • ./Tools/test-units-cuda.sh script is used to run unit tests for cuda

3. Test suite

./Tests/run-testsuite.sh script is used to run tests from test suite.

III. Release testing

CI for master branch handles common build and tests combinations, however, it doesn't cover all available build options, architectures and test launches. Yet, difference is not that critical (mostly in solver dimensions modes), so, manual testing before release is needed only for cuda (unit tests and test suite launch). For all test scenarios only GCC compiler is used, but versions may vary.

Currently supported CPU architectures:

  • x64
  • aarch32(armhf)
  • aarch64
  • riscv64
  • ppc64el

Currently supported platforms:

  • x64, sequential
  • x64, with mpi
  • x64, with cuda
  • x64, with cuda and mpi
  • aarch32(armhf), sequential
  • aarch64, sequential
  • riscv64, sequential
  • ppc64el, sequential

1. Tests of build

For tests of build this means that next command should be finished successfully for each architecture:

./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "" "" "" "" ""

However, even this might take too much time. Only next combinations are tested for release:

x64, sequential, mpi and cuda testing

./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "" "OFF,1,x" "OFF,sm" "ALL" ""
./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "" "ON,3,xyz" "OFF,sm" "ALL" ""
./Tools/test-build.sh <home_dir> <build_dir> "" "Release Debug" "ON" "" "" "f d" "OFF,1,x" "ON,sm_35" "ALL" ""
./Tools/test-build.sh <home_dir> <build_dir> "" "Release Debug" "ON" "" "" "f d" "ON,3,xyz" "ON,sm_35" "ALL" ""

x64, aarch32(armhf) cross build, sequential

./Tools/test-build.sh <home_dir> <build_dir> "arm-linux-gnueabihf-gcc,arm-linux-gnueabihf-g++" "" "" "" "" "f d" "OFF,1,x" "OFF,sm" "ALL" "arm-gcc-toolchain.cmake"

long double testing is skipped due to no diff in precision on armhf:

type	      │ lowest()	    │ min()		      │ max()
double	    │ -1.79769e+308	│ 2.22507e-308	│ 1.79769e+308
long double	| -1.79769e+308	│ 2.22507e-308	│ 1.79769e+308

x64, aarch64 cross build, sequential

./Tools/test-build.sh <home_dir> <build_dir> "aarch64-linux-gnu-gcc,aarch64-linux-gnu-g++" "" "" "" "" "" "OFF,1,x" "OFF,sm" "ALL" "arm64-gcc-toolchain.cmake"

x64, riscv64 cross build, sequential

./Tools/test-build.sh <home_dir> <build_dir> "riscv64-linux-gnu-gcc,riscv64-linux-gnu-g++" "" "" "" "" "" "OFF,1,x" "OFF,sm" "ALL" "riscv64-gcc-toolchain.cmake"

x64, ppc64el cross build, sequential

./Tools/test-build.sh <home_dir> <build_dir> "powerpc64le-linux-gnu-gcc,powerpc64le-linux-gnu-g++" "" "" "" "" "f d" "OFF,1,x" "OFF,sm" "ALL" "ppc64el-gcc-toolchain.cmake"

long double testing is skipped due to lower precision on ppc64el:

type	      │ lowest()	    │ min()		      │ max()
double	    │ -1.79769e+308	│ 2.22507e-308	│ 1.79769e+308
long double	| -1.79769e+308	│ 2.00417e-292	│ 1.79769e+308

OPTIONAL: aarch32(armhf), sequential

./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "f d" "OFF,1,x" "OFF,sm" "ALL" ""

OPTIONAL: aarch64, sequential

./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "" "OFF,1,x" "OFF,sm" "ALL" ""

OPTIONAL: riscv64, sequential

./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "" "OFF,1,x" "OFF,sm" "ALL" ""

OPTIONAL: ppc64el, sequential

./Tools/test-build.sh <home_dir> <build_dir> "" "" "" "" "" "f d" "OFF,1,x" "OFF,sm" "ALL" ""

2. Unit tests

x64, sequential, mpi and cuda testing; native launch

Next command should be finished successfully for x64 architecture

 ./Tools/test-units.sh <home_dir> <build_dir> "" "" "" "" "" "" ""

Next command should be finished successfully for x64 mpi architecture:

 ./Tools/test-units-mpi.sh <home_dir> <build_dir> "" "mpicc,mpicxx" "" "" "" ""

Next command should be finished successfully for x64 cuda architecture:

./Tools/test-units-cuda.sh <home_dir> <build_dir> "" "" "RelWithDebInfo" "ON" "" "f d" "" ""

x64, aarch32(armhf) cross build, sequential; QEMU launch

Next command should be finished successfully for armhf architecture (long double testing is skipped) with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/armhf
 sudo ./create-ubuntu-rootfs.sh armhf jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"8\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," arm-gcc-toolchain.cmake
 ./Tools/test-units.sh <home_dir> <build_dir> "" "arm-linux-gnueabihf-gcc,arm-linux-gnueabihf-g++" "" "" "" "f d" "arm-gcc-toolchain.cmake"

x64, aarch64 cross build, sequential; QEMU launch

Next command should be finished successfully for arm64 architecture with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/arm64
 sudo ./create-ubuntu-rootfs.sh arm64 jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"7\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," arm64-gcc-toolchain.cmake
 ./Tools/test-units.sh <home_dir> <build_dir> "" "aarch64-linux-gnu-gcc,aarch64-linux-gnu-g++" "" "" "" "" "arm64-gcc-toolchain.cmake"

x64, riscv64 cross build, sequential; QEMU launch

Next command should be finished successfully for arm64 architecture with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/riscv64
 sudo ./create-ubuntu-rootfs.sh riscv64 jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"9\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," riscv64-gcc-toolchain.cmake
 ./Tools/test-units.sh <home_dir> <build_dir> "" "riscv64-linux-gnu-gcc,riscv64-linux-gnu-g++" "" "" "" "" "riscv64-gcc-toolchain.cmake"

x64, ppc64el cross build, sequential; QEMU launch

Next command should be finished successfully for armhf architecture (long double testing is skipped) with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/ppc64el
 sudo ./create-ubuntu-rootfs.sh ppc64el jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"9\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," ppc64el-gcc-toolchain.cmake
 ./Tools/test-units.sh <home_dir> <build_dir> "" "powerpc64le-linux-gnu-gcc,powerpc64le-linux-gnu-g++" "" "" "" "f d" "ppc64el-gcc-toolchain.cmake"

OPTIONAL: aarch32(armhf), sequential; native launch

 ./Tools/test-units.sh <home_dir> <build_dir> "" "" "" "" "" "f d" ""

OPTIONAL: aarch64, sequential; native launch

 ./Tools/test-units.sh <home_dir> <build_dir> "" "" "" "" "" "" ""

OPTIONAL: riscv64, sequential; native launch

 ./Tools/test-units.sh <home_dir> <build_dir> "" "" "" "" "" "" ""

OPTIONAL: ppc64el, sequential; native launch

 ./Tools/test-units.sh <home_dir> <build_dir> "" "" "" "" "" "f d" ""

3. Test suite

x64, sequential, mpi and cuda testing; native launch

Next command should be finished successfully for x64 architecture:

./Tests/run-testsuite.sh 0 0

Next command should be finished successfully for x64 mpi architecture:

./Tests/run-testsuite.sh 1 0 mpicc mpicxx

Next command should be finished successfully for x64 cuda architecture (this one is not launched in CI!):

./Tests/run-testsuite.sh 0 1

Next command should be finished successfully for x64 cuda/mpi architecture (this one is not launched in CI!):

./Tests/run-testsuite.sh 1 1 mpicc mpicxx

x64, aarch32(armhf) cross build, sequential; QEMU launch

Next command should be finished successfully for armhf architecture (long double testing is skipped) with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/armhf
 sudo ./create-ubuntu-rootfs.sh armhf jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"8\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," arm-gcc-toolchain.cmake
 ./Tests/run-testsuite.sh 0 0 arm-linux-gnueabihf-gcc arm-linux-gnueabihf-g++ arm-gcc-toolchain.cmake

x64, aarch64 cross build, sequential; QEMU launch

Next command should be finished successfully for arm64 architecture with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/arm64
 sudo ./create-ubuntu-rootfs.sh arm64 jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"7\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," arm64-gcc-toolchain.cmake
 ./Tests/run-testsuite.sh 0 0 aarch64-linux-gnu-gcc aarch64-linux-gnu-g++ arm64-gcc-toolchain.cmake

x64, riscv64 cross build, sequential; QEMU launch

Next command should be finished successfully for arm64 architecture with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/riscv64
 sudo ./create-ubuntu-rootfs.sh riscv64 jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"9\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," riscv64-gcc-toolchain.cmake
 ./Tests/run-testsuite.sh 0 0 riscv64-linux-gnu-gcc riscv64-linux-gnu-g++ riscv64-gcc-toolchain.cmake

x64, ppc64el cross build, sequential; QEMU launch

Next command should be finished successfully for armhf architecture (long double testing is skipped) with cross build and launch under QEMU in rootfs:

 export ROOTFS=`pwd`/rootfs/ppc64el
 sudo ./create-ubuntu-rootfs.sh ppc64el jammy
 TOOLCHAIN_VER=$(ls $ROOTFS/usr/include/c++/)
 sed -i "s,set(TOOLCHAIN_VERSION \"9\"),set(TOOLCHAIN_VERSION \"$TOOLCHAIN_VER\")," ppc64el-gcc-toolchain.cmake
 ./Tests/run-testsuite.sh 0 0 powerpc64le-linux-gnu-gcc powerpc64le-linux-gnu-g++ ppc64el-gcc-toolchain.cmake

OPTIONAL: aarch32(armhf), sequential; native launch

./Tests/run-testsuite.sh 0 0

OPTIONAL: aarch64, sequential; native launch

./Tests/run-testsuite.sh 0 0

OPTIONAL: riscv64, sequential; native launch

./Tests/run-testsuite.sh 0 0

OPTIONAL: ppc64el, sequential; native launch

./Tests/run-testsuite.sh 0 0