CUDA-aware support #26798
Replies: 2 comments 15 replies
-
If I am reading you correctly, you may want to use: export MOOSE_MPI_COMMAND='mpiexec --opal_warn_on_missing_libcuda 0' This might work, if all you need is a way to add some arguments to If instead you need to pass arguments to your MOOSE based application I believe you're after the
I was looking for a decent doco page on our TestHarness, but this was all I could find: https://mooseframework.inl.gov/python/TestHarness.html TestHarness options/influential-environment-variables documentation could really use some TLC... #26799 |
Beta Was this translation helpful? Give feedback.
-
So I think I managed to solve the issue. It all started with me trying to get rid of this warning (after updating the framework) For which I thought it smart to update my main.C as follows: From the old version: to the new version:
That creates the error=crashed for all the tests. In addition, my fault, I never had a look at the log file from my students runs on the cluster, which, I realized this morning, did run till the end, but throwing an segfault message before finalizing. So the question that remains, is what's the right way to update the pointer to the app. Would something like the following work fine with the new syntax?
Apart from that I think we can close the issue, again, sorry for bothering you all that much and thanks for the support. |
Beta Was this translation helpful? Give feedback.
-
Dear all,
quick question: I recently installed MOOSE (+ our applications) on the leonardo booster module at CINECA in Italy. All went fine and smooth, but when trying to run the tests (failing) - errors are related to having disabled the CUDA-aware support (this is by deqfault required from the openMPI module installed locally). This said, I was wondering if there is a simple way to disable the CUDA-aware support at the TestHarness script level, or in other words, where I can integrate the --mca opal_warn_on_missing_libcuda 0 option. If not, I might go all the way to install locally openmpi. Please, keep in mind that this is not a top priority discussion, since production runs are fine (at least as long as I have tested), and it is only because I found it annoying not to be able to run the tests upon a new installation (users keep on asking me why tests are failing...).
Thanks for any advise,
mauro
Beta Was this translation helpful? Give feedback.
All reactions