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

[13_0_X] Add BX boundary checks for BXVector push_back #42329

Merged
merged 1 commit into from
Jul 23, 2023

Conversation

aloeliger
Copy link
Contributor

PR description:

Original PR description:

Quick fix requested in #42185. This includes a check in BXVector::push_back that only includes the data if it is between bxFirst_ and bxLast_, a LogWarning with some info is issued otherwise (I could remove that if complicating the buildfile and includes is undesirable).

This is being backported for #42321

PR validation:

Original PR works and prevents several BXVector related issues

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Backport of #42214

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 21, 2023

A new Pull Request was created by @aloeliger (Andrew Loeliger) for CMSSW_13_0_X.

It involves the following packages:

  • DataFormats/L1Trigger (l1)

@epalencia, @cmsbuild, @aloeliger can you please review it and eventually sign? Thanks.
@kreczko, @rovere, @eyigitba, @missirol, @thomreis, @dinyar 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

@aloeliger
Copy link
Contributor Author

Backport of #42214

@aloeliger
Copy link
Contributor Author

please test

@aloeliger aloeliger changed the title Add BX boundary checks for BXVector push_back [13_0] Add BX boundary checks for BXVector push_back Jul 21, 2023
@aloeliger aloeliger changed the title [13_0] Add BX boundary checks for BXVector push_back [13_0_X] Add BX boundary checks for BXVector push_back Jul 21, 2023
@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2fe6ad/33823/summary.html
COMMIT: f8e2fbc
CMSSW: CMSSW_13_0_X_2023-07-21-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42329/33823/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially removed 263 lines from the logs
  • Reco comparison results: 9 differences found in the comparisons
  • DQMHistoTests: Total files compared: 49
  • DQMHistoTests: Total histograms compared: 3281270
  • DQMHistoTests: Total failures: 3
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3281245
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
  • Checked 213 log files, 164 edm output root files, 49 DQM output files
  • TriggerResults: no differences found

@aloeliger
Copy link
Contributor Author

+l1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_3_X is complete. 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)

@perrotta
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 4a73811 into cms-sw:CMSSW_13_0_X Jul 23, 2023
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.

3 participants