Re #8882. Run the unit tests in random order.

Otherwise the ctest default is to run the slowest tests first, which tend to be the ones hitting the disk so they all fight for IO at the same time and get even slower. This should mitigate against that.
mantidproject · Apr 3, 2014 · 8fa04ef · 8fa04ef
1 parent 5f580e9
commit 8fa04ef
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/Code/Mantid/Build/Jenkins/buildscript b/Code/Mantid/Build/Jenkins/buildscript
@@ -55,7 +55,7 @@ make -j$BUILD_THREADS AllTests
 ###############################################################################
 # Remove any Mantid.user.properties file
 rm ~/.mantid/Mantid.user.properties
-ctest -j$BUILD_THREADS --output-on-failure -E MantidPlot
+ctest -j$BUILD_THREADS --schedule-random --output-on-failure -E MantidPlot
 # Run GUI tests serially
 #ctest --output-on-failure --timeout 30 -R MantidPlot
 
diff --git a/Code/Mantid/Build/Jenkins/buildscript.bat b/Code/Mantid/Build/Jenkins/buildscript.bat
@@ -48,7 +48,7 @@ if ERRORLEVEL 1 EXIT /B %ERRORLEVEL%
 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
 :: Run the tests
 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
-"C:\Program Files (x86)\CMake 2.8\bin\ctest.exe" -C Release -j%BUILD_THREADS% --output-on-failure -E MantidPlot
+"C:\Program Files (x86)\CMake 2.8\bin\ctest.exe" -C Release -j%BUILD_THREADS% --schedule-random --output-on-failure -E MantidPlot
 :: Run GUI tests serially
 ::ctest -C Release --timeout 30 --output-on-failure -R MantidPlot