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
ConfigBuilder
: raise an exception if the name of the alca producer exceeds the DBS schema constraints
#38189
Conversation
…ceed the DBS schema constraints
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38189/30341
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@cmsbuild, @perrotta, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: RelVals RelVals
|
as expected this fails. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0a1e75/25196/summary.html Comparison SummarySummary:
|
@cms-sw/operations-l2 I would be glad to know your opinion about this. |
+1 |
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 be automatically merged. |
ConfigBuilder
: raise an exception if the name of the alca producer exceeds the DBS schema constraintsConfigBuilder
: raise an exception if the name of the alca producer exceeds the DBS schema constraints
PR description:
This PR is half-provocative, inspired by the discussion at https://cms-talk.web.cern.ch/t/alcaprompt-datasets-not-loaded-in-dbs/11146.
Since this is the second time it happens in the CMS history (see also this old hypernew) there should be a way to stop developers to create running configurations that must be abandoned because of the DBS database schema limitations only after these are put into production.
Perhaps this could be generalized to other steps too.
PR validation:
Tried using an alca name longer than 31 chars and obtained the exception:
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A