You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, if you have ctest -j 2, there will be 2 tests running in parallel. But the auto calculation gets the maximum number of processors through ProcessorCount and defines it statically to be used in mpiexec. This leads to the cores being oversubscribed and potentially switching between the tests.
)# get 1/$TEST_OMP_THREADS the number of procs (rounded up)
On the cmake side, I am not sure if there is clear way to define this. The documentation is a bit vague on how to design this. Maybe there is some internal handling when using the PROCESSORS property. This should be investigated with the cmake team (discussion).
The text was updated successfully, but these errors were encountered:
For your case I would suggest to set the number of ranks via -DTEST_MPI_RANKS. As you said there is not a clean solution for this problem, but please let us know if you can find something. Note that tests are really meant to check correctness and not performance.
For example, if you have
ctest -j 2
, there will be 2 tests running in parallel. But the auto calculation gets the maximum number of processors throughProcessorCount
and defines it statically to be used inmpiexec
. This leads to the cores being oversubscribed and potentially switching between the tests.dbcsr/tests/CMakeLists.txt
Lines 3 to 7 in 579110d
On the cmake side, I am not sure if there is clear way to define this. The documentation is a bit vague on how to design this. Maybe there is some internal handling when using the
PROCESSORS
property. This should be investigated with the cmake team (discussion).The text was updated successfully, but these errors were encountered: