-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve testing precompilation #309
Comments
Status after much testing:
It would make sense to do sysImages in containers, esp for HPC deployment, so I'm moving that idea to #68 |
the |
the containers that we generate from the package are actually for the package and not the testing of it. There must be a way that we can pre-compile in the docker images for testing 😄 |
But you are technically never testing 2 same versions of COBREXA, so the precompiled material is not going to get re-used anyway right? |
as far as I understand, COBREXA is not recompiled with all other packages together, or is it? |
not sure. thinking about it, if we make a julia sysImage with precompiled JuMP + some solver(s), which is 90% of the compilation time anyway, we pretty much solve the problem. Does that sound OK? |
that sounds promising 👍🏼 |
Tests today:
Making the PackageCompiler image takes around 4 minutes. |
not really feasible anymore; there's julia cache (works pretty well) and most of the functionality is getting moved off the package, which will make fixing this basically unnecessary. Closing. |
This idea could potentially be improved: #303
We could try to warmup/precompile the solvers inside the docker container
The text was updated successfully, but these errors were encountered: