Open konstin opened 3 years ago
Removing UniRep from the CI would also translate to discontinuing support for it, right? I already have a review were UniRep is specifically asked, I fear more will come.
Another solution is to have a gitlab runner on a more serious machine which we can turn on and off on demand, or that we reserve for merge on dev. I'll ask Tim
I'd go with for now updating jaxlib and deactiving UniRep in CI (we can still run the tests manually on the cluster), but longterm a machine with AVX2 would be very much appreciated. Imho ideal would be if we could run CI as job on the cluster using a local disk, which would mean no need for a dedicated machine and GPU tests, but I'm not sure how well gitlab and lsf interact.
Is there an easy solution for local installations facing this issue? Is it just upgrading jaxlib with pip? Same as #162
As of now, we lack capacity to support UniRep, unfortunately. Fact is: it doesn't seem to stack up to more modern models, and given limited capacity, we rather focus on those.
try pip install jax==0.1.57 -f https://storage.googleapis.com/jax-releases/jax_releases.html
We currently depend on 0.1.57 because more recent versions need AVX2 which doesn't run on our CI, but it seems that they deleted everything older than 0.1.60: https://pypi.org/project/jaxlib/#history. Trying to resolve a new set of versions with poetry fails, I haven't check completely new installations yet.
One solution would be to update jaxlib and remove unirep from our CI.