Julius Parulek

> `integration_tests/storage/test_field_parameter.py::test_field_param_update` also fails with the same error message. > > https://github.com/equinor/ert/actions/runs/8522601524/job/23343258128?pr=7530 https://github.com/equinor/ert/actions/runs/8522710228/job/23343573807 https://github.com/equinor/ert/actions/runs/8519070513/job/23332439537 https://github.com/equinor/ert/actions/runs/8519070513/job/23332428110 https://github.com/equinor/ert/actions/runs/8524062476/job/23348244278?pr=7535 So far, no success in reproducing it locally. Have tried the following: ```sh pytest...

> @xjules Maybe it can be reproduced with the following? > > ```shell > pytest tests/integration_tests/storage/test_parameter_sample_types.py -n8 --count 100 > ``` have tried this ``` pytest tests/integration_tests/storage/test_parameter_sample_types.py -n8 --count 50...

Might be resolved by https://github.com/equinor/ert/pull/7562

Solved by https://github.com/equinor/ert/pull/7562

This might be related to the following: https://github.com/equinor/ert/pull/7901

It's a bit weird that this depends on https://github.com/equinor/ert/pull/7428 and in that one @berland suggests to wait for this one until it hits stable :thinking:

> Might be related: #7608 Yes, I think it is the same `ConnectionClosed` group error.

> Can you document in the PR or the issue why we should add an extra ensemble evaluator now, instead of converting the existing to async when the legacy JobQueue...

I have tested LSF cluster with EEAsync and it worked smoothly. Nevertheless, when cancelling some realizations are shown as running  Need to find out if it is related to...

~~TODO: fix /private/jparu/workspace/ert/kenv/root/lib64/python3.8/site-packages/ert/ensemble_evaluator/_wait_for_evaluator.py to use new async version.~~ Actually it is not relevant since this comes from `Monitor` which uses duplexer on the inside.