CDash Integration

[slabasan]

Description

Benchpark dashboard: https://my.cdash.org/index.php?project=Benchpark

Currently Working:

• After running, all gitlab CI jobs upload status to CDash
• Nightly cron at midnight runs and uploads gitlab CI jobs to CDash. This is configured through the gitlab webpage build -> pipline schedules
• show githash on dashboard
• change test_command_x to be test name.
  • working for buildname, but testname is generic gitlab. Mapping is 1:1 though.
• How to organize tests in dashboard -- nightly, experimental, continous. Maybe use labels?
  • tests organized by machine for gitlab CI. Dashboards must be added by admin on webpage before showing
• make _auth_token private env

---

Helpful page for setting up ctest with python project: https://github.com/jeffbaumes/cdash-examples/blob/master/python/CTestConfiguration.ini

To reproduce:

1. Activate venv: . /usr/workspace/benchpark-dev/benchpark-venv/$SYS_TYPE/bin/activate
2. . setup.sh
3. . workspace/setup.sh. Assumes you've run benchpark system init, benchpark experiment init, and benchpark setup
4. Run ctest -S CTestScript.cmake --debug to execute tests and upload
5. View results in cdash dashboard

Things to figure out:

• Good example dashboards: https://open.cdash.org/index.php?project=CMake and https://open.cdash.org/index.php?project=VTK
• is dashboard public yes, there's a radius button to switch from private to public

Adding/modifying core functionality, CI, or documentation:

• Update docs
• Update .github/workflows and .gitlab/ci unit tests (if needed)

[michaelmckinsey1]

Once #701 is refactored to use a python script for dryruns, we can generate the xml report for all of the dryruns. Depends on #701 Using gitlab runs instead