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

Bugfix for PR28574 #28731

Merged

Conversation

tvami
Copy link
Contributor

@tvami tvami commented Jan 11, 2020

PR description:

Fixing the issue reported in #28574 (comment)

PR validation:

Tested with runTheMatrix.py -l 7.22,7.21,7.4,7.3 -t 4 -j 8

if this PR is a backport please specify the original PR:

This is a fix for a backport, PR #28574.

@silviodonato @mmusich @tsusa

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @tvami (Tamas Vami) for CMSSW_10_6_X.

It involves the following packages:

Configuration/PyReleaseValidation

@chayanit, @cmsbuild, @pgunnell, @kpedro88, @zhenhu can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald this is something you requested to watch as well.
@davidlange6, @silviodonato, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@silviodonato
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 11, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/4202/console Started: 2020/01/11 23:53

@cmsbuild
Copy link
Contributor

+1
Tested at: 3b0c611
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6c1f87/4202/summary.html
CMSSW: CMSSW_10_6_X_2020-01-11-1100
SCRAM_ARCH: slc7_amd64_gcc700

@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-6c1f87/4202/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3212324
  • DQMHistoTests: Total failures: 3
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3211987
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@chayanit
Copy link

+1

@silviodonato
Copy link
Contributor

please test workflow 136.726

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 12, 2020

The tests are being triggered in jenkins.
Test Parameters:

@cmsbuild
Copy link
Contributor

+1
Tested at: 3b0c611
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6c1f87/4203/summary.html
CMSSW: CMSSW_10_6_X_2020-01-11-1100
SCRAM_ARCH: slc7_amd64_gcc700

@cmsbuild
Copy link
Contributor

Comparison job queued.

@silviodonato
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 8f7331c into cms-sw:CMSSW_10_6_X Jan 12, 2020
@cmsbuild
Copy link
Contributor

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

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-6c1f87/136.726_RunMuonEG2016B+RunMuonEG2016B+HLTDR2_2016+RECODR2_2016reHLT_skimMuonEG_HIPM+HARVESTDR2

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3212324
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3211989
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@boudoul
Copy link
Contributor

boudoul commented Jan 21, 2020

Hello @tvami , I start to see a dataset called /StreamExpressCosmics/Commissioning2019-PromptCalibProdSiPixel-Express-v1/ALCAPROMPT in the current MWGR , this is what you introduced here , correct ? I guess this is already a good sign - Of course there is at this point no pixel in the run, but sounds like this config is ok . You may want to x-check.

Btw @tvami and @silviodonato , it is appreciated (and useful!) to have better PR titles than this one. Titles are heavily used to understand quickly what is in a given PR (at least the context : subdetector , etc..) , so just giving a number of a PR in the title is not explicit enough to understand the purpose of this bugfix . Just a suggestion for next time - Thank you.

@mmusich
Copy link
Contributor

mmusich commented Jan 21, 2020

I start to see a dataset called /StreamExpressCosmics/Commissioning2019-PromptCalibProdSiPixel-Express-v1/ALCAPROMPT in the current MWGR , this is what you introduced here , correct ?

Hi @boudoul, no that's not correct. The sample you point out is the one created by the pixel bad components PCL, and being a PCL workflow runs at Express (in this case irrespective of the fact that pixel are in the run or not).
The new ALCARECO producers introduced here were not asked to be added to the Express configuration (that being pointless, after all there are no pixels in global run) hence we don't expect any new sample to appear in this MWGR...

@boudoul
Copy link
Contributor

boudoul commented Jan 21, 2020

oh ok, thanks I was simply confused , sorry for the noise

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

6 participants