-
Notifications
You must be signed in to change notification settings - Fork 203
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
Support parallel builds with GC3Pie (REVIEW) #1008
Conversation
Automatic reply from Jenkins: Can I test this? |
Jenkins: ok to test |
@riccardomurri: the previous comment will trigger our continuous integration server to rerun the unit tests on every set of commits being pushed in, you can check for results using the markers next to the commit ids |
@@ -421,7 +421,8 @@ def main(testing_data=(None, None, None)): | |||
command = "unset TMPDIR && cd %s && eb %%(spec)s %s" % (curdir, quoted_opts) | |||
_log.info("Command template for jobs: %s" % command) | |||
if not testing: | |||
jobs = build_easyconfigs_in_parallel(command, ordered_ecs) | |||
backend = options.job # either 'gc3pie' or 'pbs' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use options.jobbackend
Hi, just in case this becomes useful for other people following this thread: |
@riccardomurri: are you familiar with Radical-pilot, and how it's different from gc3pie? |
just to release the pressure from Riccardo, "pilot" jobs are jobs that in effect are pushed towards a node/core which then take the responsibility to pull the workload from some central service. They are very commonly found on grid platforms, as means to reduce failure complexity (if the pilot won't start, your job wouldn't have started either) and/or implement user-side job policies. |
@fgeorgates: ok, thanks |
Hi all, sorry for the late reply -- but we've had a very busy time due to a large hardware failure. I'm on vacation starting tomorrow and will be back mid-September. I guess this PR can wait. Thanks for your comments and the patience so far! Ciao, |
@riccardomurri: no worries! I'd love to see this going in soon, but vacation is waaaay more important. |
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
…eck whether output dir is NOT renamed
make GC3Pie not ignore errors
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
bump minimal required SVN revision to 4255 (which includes fix for auth=none)
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
sync with develop
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
set resource_errors_are_fatal=True in create_engine call
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
style fixes in job/backend.py and parallelbuild.py
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
sync with develop & resolve merge conflict
Refer to this link for build results (access rights to CI server needed): This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
After a lot of work by both @riccardomurri and me on this, spread out across a long time (this effort started in Aug'14!), this is finally ready to go in. We've tested this thoroughly, both on TORQUE and SLURM systems, and I've made sure that this doesn't affect the Documentation update is ready to go as well, see easybuilders/easybuild#127. Thanks a lot @riccardomurri for working together on this with us, I expect that this will quickly become a much welcomed feature. Merging to be included in EasyBuild v2.2! |
Support parallel builds with GC3Pie (REVIEW)
This is meant to be the implementation of #1006.
Basic functionality works. Configuration for the GC3Pie part is still hard-coded; I need your input as to how you would like this to be exposed in EB.
At the moment, it requires the "trunk" version of GC3Pie, soon to be released as GC3Pie 2.3.