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 sure what happened since around mid of December, but the latest libroadrunner==2.2.0 and libroadrunner-experimental==2.2.0 results in segmentation faults and dying linux kernels on most of my workflows/simulations.
I am pretty sure it is code related to the following: sys-bio/roadrunner#925 (merged beginning of January), i.e. the internal parallelization.
Please, please provide an roadrunner without any internal parallization, i.e. a single python thread on a single core! This will create issues in any multiprocessing on clusters.
The current libroadrunner=2.2.0 is not working for me at all. This is a big issue, because it breaks the scripts of all my students at the moment.
Not sure what happened since around mid of December, but the latest
libroadrunner==2.2.0
andlibroadrunner-experimental==2.2.0
results in segmentation faults and dying linux kernels on most of my workflows/simulations.I.e. I get things such as
I am pretty sure it is code related to the following: sys-bio/roadrunner#925 (merged beginning of January), i.e. the internal parallelization.
Please, please provide an roadrunner without any internal parallization, i.e. a single python thread on a single core! This will create issues in any multiprocessing on clusters.
The current libroadrunner=2.2.0 is not working for me at all. This is a big issue, because it breaks the scripts of all my students at the moment.
see sys-bio/roadrunner#963
The text was updated successfully, but these errors were encountered: