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

Allow PluginDescription default to work in release build #24656

Merged
merged 2 commits into from Sep 25, 2018

Conversation

Dr15Jones
Copy link
Contributor

The use of a default user plugin type with PluginDescription was failing when doing a full release build because it was requiring the global .edmplugincache file to already exist.
This pull request removes that requirement.

Added a configuration option to allow the PluginManager to not throw an exception in the case where it can not find any edmplugincache files.
When building a release, the construction of the final edmplugcache file does not happen until the very end of the build. This is after running edmWriteConfigs which can cause the cfi generation to fail.
For now, default user plugins must be linked in with the module using them as a default.
@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 25, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/30635/console Started: 2018/09/25 18:27

@Dr15Jones
Copy link
Contributor Author

+1

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dr15Jones (Chris Jones) for master.

It involves the following packages:

FWCore/ParameterSet
FWCore/PluginManager

@cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @wddgit this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

+1

based on Chris' tests, let's verify whether next IB is fixed (checks to be looked at anyway)

@fabiocos
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 38f1404 into cms-sw:master Sep 25, 2018
@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-24656/30635/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 705 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3146876
  • DQMHistoTests: Total failures: 1958
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3144721
  • DQMHistoTests: Total skipped: 197
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
  • Checked 133 log files, 14 edm output root files, 32 DQM output files

@fabiocos
Copy link
Contributor

@Dr15Jones @smuzaffar the build problem looks solved, and the differences observed in the comparison look to me related to other PRs merged in the meanwhile (L1T, ECAL)

@Dr15Jones
Copy link
Contributor Author

@fabiocos I agree that the differences are unrelated to this pull request.

@Dr15Jones Dr15Jones deleted the fixEdmWriteConfigsFailure branch September 27, 2018 17:47
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

3 participants