-
Notifications
You must be signed in to change notification settings - Fork 204
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
adding locking to prevent two parallel builds of the same installation directory #3009
Conversation
… same installation directory, with an option --wait-on-lock which will cause EB to wait until the lock file is removed, checking every minute for the presence of the lock file.
Mmmm, so I understand that this new code caused tests to fail, but I have trouble figuring out why... Is it because of additional output in the build output ? |
Seeking guidance here @boegel and @akesandgren. I believe we want to add the mention of the lock file in the interactive output of EB, but it seems to make all sorts of tests fail because it is unexpected output. How do I fix that ? |
I think I found it. I noticed I missed a parameter for print_msg, which (presumably) makes the output silent while in test mode. Submitted a new commit and testing with travis now. |
bug fix, code cleanup + dedicated test for installation lock
enhance lock test + appease the Hound
sort lists before comparing them in test_toy_modaltsoftname
... with an option --wait-on-lock which will cause EB to wait until the lock file is removed, checking every minute for the presence of the lock file.
This implements a feature for #2952