-
Notifications
You must be signed in to change notification settings - Fork 108
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
Adds output module validation to Express and PromptReco workflows #11175
base: master
Are you sure you want to change the base?
Conversation
Jenkins results:
|
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.
German, you didn't request for a review, but you can find some comments along the code.
|
||
Validation of output module names in the workflow | ||
""" | ||
validateOutputModules(workload) |
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.
I would suggest to move it to the super class (StdBase). Similar to how we approach this validation validateConfigCacheExists
""" | ||
Makes sure all output modules comply with DBS restrictions | ||
""" | ||
for task in workload.getAllTasks(): |
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.
we should probably define cpuOnly=True
, to avoid parsing Cleanup and LogCollect jobs.
@germanfgv German, please let me know if you need any input on this. |
Can one of the admins verify this patch? |
4fc02ab
to
4a27d0a
Compare
Jenkins results:
|
Fixes #11171
Status
not-tested
Description
Adds output module validation for T0 workflows
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
None