-
Notifications
You must be signed in to change notification settings - Fork 39
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
Submission Deferral for HammerCloud does not work anymore #8852
Comments
three are more
|
|
so only |
as reported by @stlammel [2]
see documentation of the deferral in 1
problem is that PreJob looks for a non-zero value of
CRAB_JobReleaseTimeout
in the dag boostrap classAds.The way for user to indicate that was implemented ([1]) via adding in crabConfig.
But
extraJDL
can also contain things which make DAG bootstrap fail , see #8784So I had to stop passing
extraJDL
ads to the dagman.jdl and PreJob does not find the ad anymore.Need a cleaner and explicit way to put
CRAB_JobReleaseTimeout
inDAGJob.jdl
CRABServer/src/python/TaskWorker/Actions/DagmanSubmitter.py
Line 459 in ddd6ce1
[...]
CRABServer/src/python/TaskWorker/Actions/DagmanSubmitter.py
Lines 528 to 529 in ddd6ce1
The best way would be an additional parameter in crabConfiguration, not an extrajdl classAd.
As a quick patch I can parse extraJdl from
info
in DagmanSubmitter and addCRAB_JobReleaseTimeout
if needed :-( Still ugly[1]
The text was updated successfully, but these errors were encountered: