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
In MR #1271, we saw multiple Umpire instances causing a crash because a pointer from one instance is not recognized by the other. This was caused by the combo of static Umpire libs and shared Axom libs. When Umpire logging was enabled, we got 2 log files.
We got the tests to pass by changing our CI tests to build Umpire with shared libs. But we should address the root cause of multiple Umpire instances. Maybe a better link command or rearrangement of linker switches will fix?
In MR #1271, we added reproducer tests quest_initialize.*_reallocations. When Umpire is built with static libs and Axom with shared libs, these should crash. Similar tests in mint and sidre did not reproduce the crash, indicating something about the link command in quest.
In MR #1271, we saw multiple Umpire instances causing a crash because a pointer from one instance is not recognized by the other. This was caused by the combo of static Umpire libs and shared Axom libs. When Umpire logging was enabled, we got 2 log files.
We got the tests to pass by changing our CI tests to build Umpire with shared libs. But we should address the root cause of multiple Umpire instances. Maybe a better link command or rearrangement of linker switches will fix?
In MR #1271, we added reproducer tests
quest_initialize.*_reallocations
. When Umpire is built with static libs and Axom with shared libs, these should crash. Similar tests in mint and sidre did not reproduce the crash, indicating something about the link command in quest.Possibly related to issues #865 #270 and #29.
The text was updated successfully, but these errors were encountered: