-
Notifications
You must be signed in to change notification settings - Fork 17
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
CI/Docker build: faster or parallel #286
Comments
I'm not sure #287 actually does what we want. This looks like we still have races:
Or in another variant:
Or yet another:
|
The above was from three different variants of our CI. I am also seeing strange effects in native installations – if I enable Until we know what's going on, we should perhaps disable parallel build (and hope we are still under 1h due to #287 speedups). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
maximum-cuda
, we recently broke the 1h build time boundary for CircleCI free accounts. Hence the attempt to usemake -j
again to reduce it (the VMs are multi-core, so this should work in principle).But it seems that we have a race condition which has not been detected yet:
This looks like multiple
pip
calls on the same venv clash. Maybe we need to synchronize these calls in the same way we do forgit
calls.The text was updated successfully, but these errors were encountered: