Closed jonathan-eq closed 1 year ago
We used git bisect to find the commit in question. It changed pybind for some C code, which could lead to resource starvation. We are suspecting that the reason we only observe the bug in Azure is that the resources there are already sparse as is.
Describe the bug It seemed like between release 2023.08.rc3 and rc4, something made ert taking 3x as long to even get the realization boxes showing. We have confirmed the jobs are loaded by checking qstat -fu. Between those release candidates, ert was upgraded from 5.1.0-rc0 to ert 6.0.0-rc1, maybe this is related?
To reproduce Steps to reproduce the behaviour: