Skip to content

Use single CI variable for enabling all Valgrind tests

Right now our Valgrind tests are a bit inconsistent:

  • test-cta-valgrind is triggered on a schedule
  • The Valgrind DB tests are triggered when VALGRIND_DB_UNIT_TESTS is set to TRUE

The scheduled part is a bit problematic, because it means that our (currently failing) valgrind tests trigger on every scheduled pipeline run.

I will be changing this to a single variable VALGRIND_UNIT_TESTS, which will determine whether to run tests with valgrind or not. This way, only a single nightly pipeline will have the valgrind tests enabled.