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
migrate CondCore/PopCon
away from deprecated EDAnalyzer
API
#35469
migrate CondCore/PopCon
away from deprecated EDAnalyzer
API
#35469
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35469/25624
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
236040c
to
9cf4a29
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35469/25625
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @ggovi, @francescobrivio, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8cfb91/19238/summary.html Comparison SummarySummary:
|
test parameters:
|
@cmsbuild , please test |
@tvami, sorry what's the point of re-testing? |
Oh, sorry, I just saw that the test results came back normal, and that's the opposite of what you were reporting in the description so I thought that those unit test have not been run. But now I dont understand, what changed so that the unit tests are fine now? |
@tvami it seems you did not read carefully the description |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8cfb91/19246/summary.html Comparison SummarySummary:
|
+alca |
+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) |
@mmusich BTW I confirm that - in absence of the proper db key ( the bot has one ) - the above O2O unit test cannot be executed... |
+1 |
resolves cms-AlCaDB/AlCaTools#37
PR description:
Title says it all.
PR validation:
After checking dependencies with
git cms-checkdeps -a
it still compiles.Running the unit tests for all the checked out packages there are multiple errors
all seemingly related to:
which looks like an intrinsic limitation of running the O2O test from the lambda user.
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A