Commit 9c292007 authored by Robert Maynard's avatar Robert Maynard

UnitTestBoundingIntervalHierarchy handles systems under load better

The UnitTestBoundingIntervalHierarchy has historically had problems
when the machine is already under-load when the algorithm is executed.
By limiting the number of openMP threads the test uses we can
reduce the amount of CPU time slicing that this test causes.
parent 671c1df5
...@@ -116,6 +116,13 @@ void TestBoundingIntervalHierarchy(vtkm::cont::DataSet dataSet, vtkm::IdComponen ...@@ -116,6 +116,13 @@ void TestBoundingIntervalHierarchy(vtkm::cont::DataSet dataSet, vtkm::IdComponen
void RunTest() void RunTest()
{ {
//If this test is run on a machine that already has heavy
//cpu usage it will fail, so we limit the number of threads
//to avoid the test timing out
omp_set_num_threads(std::min(4, omp_get_max_threads()));
TestBoundingIntervalHierarchy(ConstructDataSet(16), 3); TestBoundingIntervalHierarchy(ConstructDataSet(16), 3);
TestBoundingIntervalHierarchy(ConstructDataSet(16), 4); TestBoundingIntervalHierarchy(ConstructDataSet(16), 4);
TestBoundingIntervalHierarchy(ConstructDataSet(16), 6); TestBoundingIntervalHierarchy(ConstructDataSet(16), 6);
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment