-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simulation freezes #5494
Comments
Sigh, one of my most favorite parallel deadlocks in opm-flow: 7 processes in
and 1 threw an unexpected exception:
I think this due to COMPDAT in ACTIONX. Outside of ACTIONX this check is performed on process 0 and the cell is known there. Now this is performed on the parallel loadbalanced grid (without the our futureComletions) and the cell is maybe on another process? The real problem here is that our simulator should fail gracefully and not deadlock even without your upcoming PR #5488 which is closing this. |
Yes, true, then the simulator should stop. |
I wrote a test for sth different and on Jenkins, the simulation froze:
Datafile: https://github.com/lisajulia/opm-tests/blob/8b84e28bd63d705ec659976a789cbc5cd7f0a80a/actionx/ACTIONX_COMPDAT_SHORT.DATA
Log file from Jenkins with frozen simulation, ended by a timeout then: https://ci.opm-project.org/job/opm-simulators-PR-builder/6452/testReport/junit/(root)/mpi/compareSeparateECLFiles_flow_actionx_compdat_8_procs/
Flow compiled with the following commits:
opm-common: d075bc889ead20424c695382a077275ddb1c66a3
opm-models: 29582a9f59feec1c9d04286977ab6adef89b12e3
opm-grid: bc501ad7f48676918c594d0c8dd42c405958f758
opm-simulators: ed5f371
I ran flow on 8 processes.
In case this error is gone when testing this again, please close!
The text was updated successfully, but these errors were encountered: