-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add warning if WF name will be too long for submission #29621
Add warning if WF name will be too long for submission #29621
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29621/14971
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. It involves the following packages: Configuration/PyReleaseValidation @chayanit, @cmsbuild, @wajidalikhan, @pgunnell, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
|
||
|
||
if self.testMode and self.countLongWFName>0: | ||
print("\n*** FIX NEEDED BEFORE INJECTION: "+str(self.countLongWFName)+" candidate workflows have too long name (>81 characters) ***") |
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.
raise an exception?
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.
Fix the text. This is for warning only that the workflows can't be submitted later.
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.
Is there a situation where we want to allow those long workflow names? If not, I still think an exception would be better. That way, any PR creating an unnecessarily long workflow name must be fixed.
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.
As mentioned in the PR description, if someone would like to use "--wm init" to dump the configuration to run local-test only, we should not break it. This warning is targeted for people (like PdmV) who will submit relvals later, using "--wm submit, force" after "--wm init".
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@kpedro88 does the last version of the code address your comments? |
+1 |
+upgrade |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The character length of computing workflow is limited to 100 characters. The workflow name composes of 3 main parts:
_200425_064221_5181
.This PR is to check if len(username_RequestString) is longer than 81 characters or not, then print the warning at the end when
--wm init
is used.The goal is not to break the
--wm init
process, as one may need to just dump config for testing using any release (including IB). This PR just provides the warning in case someone would like to inject workflows later. Without this test, the injection will break when--wm force
is used. However, some of the workflows will be submitted if they come before problematic workflows.PR validation:
Test with 11_1_0_pre6:
runTheMatrix.py --what standard -l 136.886,136.7611,136.756 -t 8 -b 'DQM8CoresData' --label 'DQM8CoresData1234567890' --wm init
workflow 136.866 is OK in this test,
During injection, 136.866 will pass the injection, then break when 136.7611 injection is done.
if this PR is a backport please specify the original PR and why you need to backport that PR:
No need to backport.