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

Modules will see end transition if they saw a begin transition #21108

Merged
merged 2 commits into from Nov 1, 2017

Conversation

Dr15Jones
Copy link
Contributor

In the case where an exception occurs during a begin Run/LuminosityBlock transition we make sure that modules which saw that transition will also see the related end transition. This is accomplished by requiring all modules to see a transition once that transition has started. In this way we do not have to record which modules have seen which transitions (since it will be all or none).
If the exception happened during the global part of the transition, we do not then run the stream part of the transition in order to attempt to minimize the time to end the application.

If we call a begin Run or begin LuminosityBlock transition we need to call the corresponding end transition.
If a global begin transition fails, we skip the corresponding begin/end stream transitions.
We only call writeRun or writeLumi if the full transition succeeds.
Even if the parent process throws an exception during a Run or LuminosityBlock transition, we still run the transition for the SubProcess.
This helps guarantee that if a module gets a begin transition call it will also receive an end transition call.
@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/PR-21108/1739

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

FWCore/Framework

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

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 31, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/24096/console Started: 2017/11/01 02:03

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

Comparison job queued.

@Dr15Jones
Copy link
Contributor Author

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

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

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2017

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2838442
  • DQMHistoTests: Total failures: 119
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2838152
  • DQMHistoTests: Total skipped: 171
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 10 edm output root files, 26 DQM output files

@davidlange6
Copy link
Contributor

merge

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