Julius Parulek comments

Results 86 comments of


                                            Julius Parulek

Progressbar in Detailed Progress does not update after pressing kill simulations

Closing this issue as it has been fixed since.

After clicking `Kill realizations` realizations with state `Waiting` are submitted before being stopped.

This might be already solved by the new Scheduler Queue system.

After clicking `Kill realizations` realizations with state `Waiting` are submitted before being stopped.

Can this be closed @oyvindeide ?

Ee new

Closing this one as this was for testing sake only

Check of 2024.05 contains scheduler fixes

Update: stable now contains all the current bug-fixes. Will keep this open until we get reports on run.

Improve ambiguous logging when max_submit is 1

Suggestion what to log: - exit code of the last successful / failed job - the last know state

Improve ambiguous logging when max_submit is 1

Apparently, when mimicking NFS syncing issues, we will not get any logs too: Copy from @eivindjahren message: --- If `_ert_forward_model_runner crashes` (for instance due to missing jobs.json because of NFS...

Improve ambiguous logging when max_submit is 1

The logging might be already fixed by 50a4421. Need to just test.

Improve ambiguous logging when max_submit is 1

What we should do is to "find out" that the job does not run and get the lsf stdout into the logs.

No running event loop error observed when doing heavy update

Now I start to understand why this happens. Not sure if this is an inherit flakiness of checking `self._connection.open`which should be the proper way of testing it before calling connection.close()...