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
Describe the bug
Terminate experiment does not do anything when jobs are pending.
To reproduce
Steps to reproduce the behaviour:
Login to an onprem or Azure node.
Run ERT in gui mode (I tried fmu-drogon/drogon_design.ert)
Maybe choose a queue that is very slow to respond, like short, or for LSF use an outrageous memory requirement like QUEUE_OPTION LSF LSF_RESOURCE rusage[mem=200000]
Run an ensemble experiment
While realizations are still in "Pending" state, click "Terminate experiment" and "Yes" in the dialoge box
Observe that nothing happens.
Observe that if the close-button in the upper right corner of the window is clicked, the same dialoge box appears, and if clicking yes, the run-dialogue window is closed. Realizations are still not killed, and the main Ert window has some errors: "Run Experiment" cannot be clicked, and the main window cannot be closed.
Expected behaviour qdel/bkill commands should be initiated and Ert should tear down the ensemble experient
Environment
OS: RHEL7
ERT/Komodo release: bleeding as of 2024-05-13
Python version: 3.8
Remote/HPC execution involved: yes
The text was updated successfully, but these errors were encountered:
The problem is that killing of realizations depends on events being sent, but there are no events while all realizations are pending. The code is stuck in the async for statement in:
Describe the bug
Terminate experiment does not do anything when jobs are pending.
To reproduce
Steps to reproduce the behaviour:
short
, or for LSF use an outrageous memory requirement likeQUEUE_OPTION LSF LSF_RESOURCE rusage[mem=200000]
Expected behaviour
qdel
/bkill
commands should be initiated and Ert should tear down the ensemble experientEnvironment
The text was updated successfully, but these errors were encountered: