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
Not only is this consistent with blt_add_test, but this enables e.g., creating your own configurations that specific benchmarks should be run on. For instance, I would like to create a "Multinode" configurations where only tests / benchmarks that require multiple nodes should be run (e.g., to benchmark inter-node bandwidth). This way I can create a Jenkins job or the like that only runs those tests when I allocate two+ nodes for a job.
skyreflectedinmirrors
changed the title
blt_add_benchmark should take CONFIGURATIONS argument
blt_add_benchmark should take CONFIGURATIONS and OMP_NUM_THREADS arguments
May 17, 2023
E.g., here:
blt/cmake/BLTMacros.cmake
Line 937 in 553a902
Not only is this consistent with
blt_add_test
, but this enables e.g., creating your own configurations that specific benchmarks should be run on. For instance, I would like to create a "Multinode" configurations where only tests / benchmarks that require multiple nodes should be run (e.g., to benchmark inter-node bandwidth). This way I can create a Jenkins job or the like that only runs those tests when I allocate two+ nodes for a job.Today, I have to do something like:
I think this would be a minimally invasive PR, and I'd be happy to work on it if y'all agree.
The text was updated successfully, but these errors were encountered: