Skip to content
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

Move all PCLConfigPlugins sources to plugins #40245

Merged
merged 1 commit into from Dec 8, 2022

Conversation

guitargeek
Copy link
Contributor

This is a follow up to #39649.

In that PR, some shared code in the plugins directory of CondCore/PCLConfigPlugins got factored out and was put into a new header file that was placed in the interface directory.

That resulted in some inconsistencies in the build configuration, because the interface and src directories actually didn't correspond to a normal library, but also to a plugins library because of the <flags EDM_PLUGIN="1"/> in the BuildFile!

Hence, one plugin library included the header files from another plugin library, which should not be done. In particular, it confused my unused dependency checker, because you can't declare another plugins library as a dependency. That forced us to declare the dependencies of the CondCore/PCLConfigPlugins plugins library also in CondCore/PCLConfigPlugins, which caused false positives in the unused-dependency checks.

This commit fixes the situation by moving the header file into the plugins directory. To avoid confusing a plugin library with a regular library in the future, the plugin library that was defined in the top-level of CondCore/PCLConfigPlugins got also moved to be another build target in the plugins subdirectory, in a way such that the compiled library name doesn't change.

This is a follow up to #39649.

In that PR, some shared code in the `plugins` directory of
CondCore/PCLConfigPlugins got factored out and was put into a new header
file that was placed in the `interface` directory.

That resulted in some inconsistencies in the build configuration,
because the `interface` and `src` directories actually didn't correspond
to a normal library, but also to a plugins library because of the
`<flags EDM_PLUGIN="1"/>` in the BuildFile!

Hence, one plugin library included the header files from another plugin
library, which should not be done. In particular, it confused my unused
dependency checker, because you can't declare another plugins library as
a dependency. That forced us to declare the dependencies of the
`CondCore/PCLConfigPlugins` plugins library also in
`CondCore/PCLConfigPlugins`, which caused false positives in the
unused-dependency checks.

This commit fixes the situation by moving the header file into the
`plugins` directory. To avoid confusing a plugin library with a regular
library in the future, the plugin library that was defined in the
top-level of `CondCore/PCLConfigPlugins` got also moved to be another
build target in the `plugins` subdirectory, in a way such that the
compiled library name doesn't change.
@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 6, 2022

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40245/33299

  • This PR adds an extra 12KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 6, 2022

A new Pull Request was created by @guitargeek (Jonas Rembser) for master.

It involves the following packages:

  • CondCore/PCLConfigPlugins (db)

@malbouis, @cmsbuild, @saumyaphor4252, @ggovi, @francescobrivio, @tvami can you please review it and eventually sign? Thanks.
@mmusich this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@mmusich
Copy link
Contributor

mmusich commented Dec 6, 2022

test parameters:

  • workflows = 1001.0, 1001.2

@guitargeek
Copy link
Contributor Author

Thanks @mmusich! Seems the bot hasn't started the tests yet. Maybe you got to change the parameters and ask for the tests to start in two separate comment?

@mmusich
Copy link
Contributor

mmusich commented Dec 6, 2022

I am not asking the bot to test anything, that's intentional.

@guitargeek
Copy link
Contributor Author

Ah alright, thanks for clarifying! Just wanted to make sure

@tvami
Copy link
Contributor

tvami commented Dec 6, 2022

@cmsbuild , please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2022

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-a447e3/29494/summary.html
COMMIT: d59178d
CMSSW: CMSSW_13_0_X_2022-12-06-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/40245/29494/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 1 differences found in the comparisons
  • DQMHistoTests: Total files compared: 49
  • DQMHistoTests: Total histograms compared: 3421398
  • DQMHistoTests: Total failures: 152
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3421224
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
  • Checked 213 log files, 159 edm output root files, 49 DQM output files
  • TriggerResults: no differences found

@tvami
Copy link
Contributor

tvami commented Dec 7, 2022

+db

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 7, 2022

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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@rappoccio
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 8dd39e4 into cms-sw:master Dec 8, 2022
@guitargeek guitargeek deleted the pcl_1 branch January 2, 2023 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants