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
Fix for O2O tests requiring to read runinfo payload #35472
Fix for O2O tests requiring to read runinfo payload #35472
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35472/25630
|
A new Pull Request was created by @ggovi for master. It involves the following packages:
@ggovi, @malbouis, @cmsbuild, @tvami, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d39c77/19243/summary.html Comparison SummarySummary:
|
+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 now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The O2O test workflow is modified by adding in the target sqlite export one iov, with the original since value of the 'max iov pointing to a payload with boost version compatible with the underlying release'
For iovs of run time-type, this is allowing to have an upper run value where the corresponding RunInfo payload will be readable by the same release.
These changes correspond to commit 445f542 in #35442
Tested with all O2Os integration tests.