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
Clean BuildFiles before DataFormats #30139
Conversation
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @guitargeek (Jonas Rembser) for master. It involves the following packages: Alignment/APEEstimation @perrotta, @pgunnell, @andrius-k, @chayanit, @schneiml, @wajidalikhan, @tlampen, @christopheralanwest, @tocheng, @cmsbuild, @kmaeshima, @jfernan2, @fioriNTU, @slava77, @ggovi, @pohsun, @santocch can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
+1 |
+1 |
Hi @pieterdavid, I'm a bit confused now because this PR got the |
Hi @guitargeek thanks for checking, but there's no need to delay this (I brought it up because having it in last week's pre-release would have been convenient, but we will manage). |
+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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
code-checks |
The code-checks are being triggered in jenkins. |
+1 |
PR description:
Another quick partially automatic BuildFile cleaning PR in the style of many before (for example #29906), this time covering all subsystems before DataFormats.
Some plugins which were not merged with their header files actually had their header files in the
interface
directory, even though they are not needed by the library (only the plugins). This confuses my BuildFile/includes checker, which does not expect this entanglement between the library and the plugins. For these cases, I merged the plugin header with thecc
file.PR validation:
CMSSW compiles. It was checked that all newly added dependencies are actually required by the package with
git grep
.