#2023: CarpetInterp hangs with openmpi ------------------------+--------------------------------------------------- Reporter: anonymous | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Resolution: | Keywords: OpenMPI, Carpet ------------------------+---------------------------------------------------
Comment (by hinder):
Unfortunately we were unsuccessful in reproducing it in a small test case; it was a full SpEC run. There was no hyperthreading or OpenMP. In the runs where it was not reproducible, are the numerical results identical in each different copy of the run, or does the code make different decisions based, e.g. on timing, in each case? SpEC has several places where it chooses the best algorithm based on runtime performance, and this meant that the code paths were different. That is why it didn't affect all the runs. Only when we disabled all these options did we manage to get something to fail reliably.