Make quest testing faster

[BradWhitlock]

I keep running into problems with CI testing failing because it runs out of time. The CI nodes are weak. Still, some of these tests take excessive time.

Modes like "Debug - llvm@19.0.0,no raja and umpire" and "Debug - llvm@19.0.0 shared,no profiling" exhibit a few really slow tests:

• Split the tests?
• Only run them in Release mode?
• Increase CI time limit?

[kennyweiss]

Can you try to run those again serially?

> ctest -R quest_regression

I think those tests are actually not that bad and the problem is in CTest launching everything at the same time.

That's what I was trying to fix with llnl/blt#749 and #1749

[BradWhitlock]

These failures seem to be in the Azure tests. Do they have a command line where I can run "ctest -R quest_regression"? I can run that test locally and it's more like 7 seconds but that is not where it's running out of time.

[kennyweiss]

If it's just to temporarily check the non-parallel test runtimes and see what's getting stuck,
you could modify this line and remove the -j flag:

axom/scripts/github-actions/linux-build_and_test.sh

Line 48 in f28fc33

make CTEST_OUTPUT_ON_FAILURE=1 test ARGS='-T Test --output-on-failure -j$NUM_BUILD_PROCS'

[BradWhitlock]

I tried making that change. The test suite passed that time. Still, the numbers for these tests did not change too much. It makes me think that there is enough variability in how long the tests take to run (file system?) that we sometimes bump up against the CI time limit.