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

Clean BuildFiles in L1Trigger #31548

Merged
merged 1 commit into from
Sep 25, 2020
Merged

Clean BuildFiles in L1Trigger #31548

merged 1 commit into from
Sep 25, 2020

Conversation

guitargeek
Copy link
Contributor

PR description:

Another quick partially automatic BuildFile cleaning PR in the style of many before (for example #31532).

As always, only the dependencies which are not included in any of the sources are removed, so these changes are orthogonal and complementary to the recent PRs which added all packages that are actually included.

PR validation:

CMSSW compiles. It was checked that all newly added dependencies are actually required by the package with git grep.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31548/18558

  • This PR adds an extra 88KB to repository

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

L1Trigger/CSCCommonTrigger
L1Trigger/CSCTrackFinder
L1Trigger/CSCTriggerPrimitives
L1Trigger/DTBti
L1Trigger/DTSectorCollector
L1Trigger/DTTraco
L1Trigger/DTTrigger
L1Trigger/DTTriggerPhase2
L1Trigger/DTTriggerServerPhi
L1Trigger/DTTriggerServerTheta
L1Trigger/DTUtilities
L1Trigger/GlobalCaloTrigger
L1Trigger/GlobalMuonTrigger
L1Trigger/GlobalTrigger
L1Trigger/GlobalTriggerAnalyzer
L1Trigger/HardwareValidation
L1Trigger/L1CaloTrigger
L1Trigger/L1ExtraFromDigis
L1Trigger/L1GctAnalyzer
L1Trigger/L1TCaloLayer1
L1Trigger/L1TCalorimeter
L1Trigger/L1TCommon
L1Trigger/L1TGEM
L1Trigger/L1TGlobal
L1Trigger/L1TMuon
L1Trigger/L1TMuonBarrel
L1Trigger/L1TMuonCPPF
L1Trigger/L1TNtuples
L1Trigger/L1TTrackMatch
L1Trigger/L1TTwinMux
L1Trigger/Phase2L1ParticleFlow
L1Trigger/RPCTechnicalTrigger
L1Trigger/RPCTrigger
L1Trigger/RegionalCaloTrigger
L1Trigger/Skimmer
L1Trigger/TrackFindingTMTT
L1Trigger/TrackFindingTracklet
L1Trigger/TrackTrigger
L1Trigger/TrackerDTC
L1TriggerConfig/DTTPGConfig
L1TriggerConfig/DTTPGConfigProducers
L1TriggerConfig/GMTConfigProducers
L1TriggerConfig/L1CSCTPConfigProducers
L1TriggerConfig/L1GeometryProducers
L1TriggerConfig/L1TConfigProducers
L1TriggerConfig/RPCTriggerConfig
L1TriggerConfig/Utilities
L1TriggerOffline/L1Analyzer

@cmsbuild, @rekovic, @benkrikler, @kpedro88 can you please review it and eventually sign? Thanks.
@erikbutz, @kreczko, @battibass, @sviret, @valuev, @ptcox, @Martin-Grunewald, @dildick, @thomreis this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@dildick
Copy link
Contributor

dildick commented Sep 23, 2020

Hi Jonas, there a few packages that I maintain within the L1-trigger. What prevents scram b code-checks from picking up the missing buildfiles?

@guitargeek
Copy link
Contributor Author

Hello Sven! I would like to give you an answer, but I don't really understand the question. Are you wondering why the changes that I suggest in this PR are not just suggested by the code checks?

All I can say is that I intended to improve the modularity of CMSSW with these PRs. My original motivation was that I wanted to build parts of CMSSW independently of the rest, and on the way I wrote a script that removes unused dependencies from the BuildFiles. In the last year, I occasionally made PRs for different subsystems after running the script, and L1Trigger is actually the only remaining subsystem for which I didn't make a PR so far.

However, when you automatically remove the unused dependencies like that, you occasionally break packages that didn't declare all their dependencies but relied on the unused dependency declarations in packages further up in the dependency hierarchy that are now removed. That's why this PR also adds a few lines.

@dildick
Copy link
Contributor

dildick commented Sep 23, 2020

I think you largely answered my question. Thanks!

In the future though, if someone were to (accidentally) remove a <use name > statement in a buildfile that you previously fixed, would scram b code-checks prevent that from happening? Or would your script have to be interfaced with scram?

@guitargeek
Copy link
Contributor Author

If someone would accidentally remove a <use name > that I added, it will just not compile. The "worst" that can happen is that someone accidentally puts back a unused dependency that I removed, but this can be very easily spotted in PR reviews.

My script is too inefficient and not flexible enough to consider using it with scram; it's really more of a one-shot thing to get rid of a massive amount of unused dependencies that have accumulated over the years.

@dildick
Copy link
Contributor

dildick commented Sep 23, 2020

Ok. Thanks.

@silviodonato
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 23, 2020

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+1
Tested at: 1ea3be0
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6f608e/9521/summary.html
CMSSW: CMSSW_11_2_X_2020-09-23-1100
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6f608e/9521/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2539438
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2539409
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 34 files compared)
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@kpedro88
Copy link
Contributor

+upgrade

@rekovic
Copy link
Contributor

rekovic commented Sep 25, 2020

+1

@cmsbuild
Copy link
Contributor

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

@silviodonato
Copy link
Contributor

+1

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.

6 participants