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

Removal of hardcoded testing L1T tag and move it to GT #36408

Merged
merged 2 commits into from Dec 21, 2021

Conversation

tvami
Copy link
Contributor

@tvami tvami commented Dec 8, 2021

PR description:

Instead of #35554

Also resolves #27393

Original description
"This PR removes part of the configuration of L1T Calo which retrieves conditions from a specific location (instead of via GT) and which is deprecated for a while (non-used since we moved away from hacking conditions)."

Extra in this PR is the addition of this tag to the GT.

For the future:

  • This tag is for testing purposes, thus it should be fed to the code via a test python cfg file and not hardcoded in the cpp code nor really read from the GT

Here is the list of diffs wrt to the queue:

https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun1_design_Queue/123X_mcRun1_design_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun1_realistic_Queue/123X_mcRun1_realistic_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun1_HeavyIon_Queue/123X_mcRun1_HeavyIon_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_startup_Queue/123X_mcRun2_startup_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_asymptotic_l1stage1_Queue/123X_mcRun2_asymptotic_l1stage1_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_design_Queue/123X_mcRun2_design_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_asymptotic_preVFP_Queue/123X_mcRun2_asymptotic_preVFP_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_asymptotic_Queue/123X_mcRun2_asymptotic_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2cosmics_asymptotic_deco_Queue/123X_mcRun2cosmics_asymptotic_deco_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_HeavyIon_Queue/123X_mcRun2_HeavyIon_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun2_pA_Queue/123X_mcRun2_pA_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun2_Queue/123X_dataRun2_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun2_HEfail_Queue/123X_dataRun2_HEfail_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun2_relval_Queue/123X_dataRun2_relval_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun2_PromptLike_HI_Queue/123X_dataRun2_PromptLike_HI_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun3_HLT_Queue/123X_dataRun3_HLT_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun2_HLT_relval_Queue/123X_dataRun2_HLT_relval_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun3_Express_Queue/123X_dataRun3_Express_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun3_Prompt_Queue/123X_dataRun3_Prompt_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_dataRun3_Queue/123X_dataRun3_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mc2017_design_Queue/123X_mc2017_design_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mc2017_realistic_Queue/123X_mc2017_realistic_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mc2017cosmics_realistic_deco_Queue/123X_mc2017cosmics_realistic_deco_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mc2017cosmics_realistic_peak_Queue/123X_mc2017cosmics_realistic_peak_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018_design_Queue/123X_upgrade2018_design_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018_realistic_Queue/123X_upgrade2018_realistic_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018_realistic_RD_Queue/123X_upgrade2018_realistic_RD_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018_realistic_HI_Queue/123X_upgrade2018_realistic_HI_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018_realistic_HEfail_Queue/123X_upgrade2018_realistic_HEfail_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018cosmics_realistic_deco_Queue/123X_upgrade2018cosmics_realistic_deco_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_upgrade2018cosmics_realistic_peak_Queue/123X_upgrade2018cosmics_realistic_peak_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021_design_Queue/123X_mcRun3_2021_design_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021_realistic_Queue/123X_mcRun3_2021_realistic_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021cosmics_realistic_deco_Queue/123X_mcRun3_2021cosmics_realistic_deco_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021_realistic_HI_Queue/123X_mcRun3_2021_realistic_HI_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2023_realistic_Queue/123X_mcRun3_2023_realistic_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2024_realistic_Queue/123X_mcRun3_2024_realistic_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun4_realistic_Queue/123X_mcRun4_realistic_v2

PR validation:

Previously failing addOnTest pass

addOnTests.py -j 8

if this PR is a backport please specify the original PR and why you need to backport that PR:

N/A

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

assign alca

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

@cmsbuild , please test

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

code-checks

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 8, 2021

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36408/27221

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 8, 2021

New categories assigned: alca

@yuanchao,@francescobrivio,@malbouis,@tvami you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 8, 2021

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

It involves the following packages:

  • L1Trigger/L1TCalorimeter (l1)

@malbouis, @yuanchao, @rekovic, @francescobrivio, @cecilecaillol, @tvami can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @missirol this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

@smuzaffar tests are taking more than 11 hours, is there something wrong with the bot? Thanks!

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

@smuzaffar tests are taking more than 11 hours, is there something wrong with the bot? Thanks!

Same thing is happening in #36409

@smuzaffar
Copy link
Contributor

all resources to test are busy, I am afraid you have to wait.

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 8, 2021

-1

Failed Tests: RelVals RelVals-INPUT AddOn
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d73f32/21085/summary.html
COMMIT: f0bb5f6
CMSSW: CMSSW_12_3_X_2021-12-07-2300/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/36408/21085/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

  • 136.731136.731_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2_skimSinglePh/step2_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2_skimSinglePh.log

RelVals-INPUT

  • 136.722136.722_RunDoubleEG2016B+RunDoubleEG2016B+HLTDR2_2016+RECODR2_2016reHLT_skimDoubleEG_HIPM+HARVESTDR2_skimDoubleEG/step2_RunDoubleEG2016B+RunDoubleEG2016B+HLTDR2_2016+RECODR2_2016reHLT_skimDoubleEG_HIPM+HARVESTDR2_skimDoubleEG.log
  • 136.721136.721_RunHLTPhy2016B+RunHLTPhy2016B+HLTDR2_2016+RECODR2_2016reHLT_HIPM+HARVESTDR2/step2_RunHLTPhy2016B+RunHLTPhy2016B+HLTDR2_2016+RECODR2_2016reHLT_HIPM+HARVESTDR2.log
  • 136.723136.723_RunDoubleMuon2016B+RunDoubleMuon2016B+HLTDR2_2016+RECODR2_2016reHLT_HIPM+HARVESTDR2/step2_RunDoubleMuon2016B+RunDoubleMuon2016B+HLTDR2_2016+RECODR2_2016reHLT_HIPM+HARVESTDR2.log
Expand to see more relval errors ...

AddOn Tests

  • hlt_data_Fake2cmsDriver.py RelVal -s L1REPACK:Full --data --scenario=pp -n 10 --conditions auto:run2_hlt_Fake2 --relval 9000,50 --datatier "RAW" --eventcontent RAW --customise=HLTrigger/Configuration/CustomConfigs.L1T --era Run2_2016 --fileout file:RelVal_Raw_Fake2_DATA.root --filein /store/data/Run2016B/JetHT/RAW/v1/000/272/762/00000/C666CDE2-E013-E611-B15A-02163E011DBE.root : FAILED - time: date Wed Dec 8 15:00:38 2021-date Wed Dec 8 14:56:02 2021 s - exit: 35584
  • hlt_mc_Fake2cmsRun /cvmfs/cms-ib.cern.ch/week0/slc7_amd64_gcc900/cms/cmssw/CMSSW_12_3_X_2021-12-07-2300/src/HLTrigger/Configuration/test/OnLine_HLT_Fake2.py realData=True globalTag=@ inputFiles=@ : FAILED - time: date Wed Dec 8 15:00:38 2021-date Wed Dec 8 14:56:02 2021 s - exit: 21504
  • hlt_data_Fake2
----- Begin Fatal Exception 08-Dec-2021 15:00:37 CET-----------------------
An exception of category 'FileOpenError' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing input source of type PoolSource
   [2] Calling RootInputFileSequence::initTheFile()
   Additional Info:
      [a] Input file file:RelVal_Raw_Fake2_DATA.root could not be opened.
      [b] Fatal Root Error: @SUB=TStorageFactoryFile::ReadBuffer
read from Storage::xread returned 262. Asked to read n bytes: 300 from offset: 0 with file size: 262

----- End Fatal Exception -------------------------------------------------

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

Input file file:RelVal_Raw_Fake2_DATA.root could not be opened.

I guess we should just test again? @smuzaffar

@mmusich
Copy link
Contributor

mmusich commented Dec 8, 2021

I guess we should just test again? @smuzaffar

There's a tonne of segfaults in L1TStage2Layer2Producer:simCaloStage2Digis (see e.g. log). I doubt that will go away re-testing.
FWIW, I still think the right thing to do is to add instead the payloads to GlobalTag: #35554 (comment)

@tvami
Copy link
Contributor Author

tvami commented Dec 8, 2021

There's a tonne of segfaults in L1TStage2Layer2Producer:simCaloStage2Digis (see e.g. log). I doubt that will go away re-testing.

But this means that the HLT menu has m_useStaticConfig on True, right? It should not be, see "use static config for fw testing"

@mmusich
Copy link
Contributor

mmusich commented Dec 8, 2021

But this means that the HLT menu has m_useStaticConfig on True, right?

I don't see what the HLT menu has anything to do with it. That's in the configuration of L1TStage2Layer2Producer which should be run in the L1REPACK step.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36408/27482

@cmsbuild
Copy link
Contributor

Pull request #36408 was updated. @malbouis, @yuanchao, @epalencia, @rekovic, @francescobrivio, @cecilecaillol, @tvami can you please check and sign again.

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d73f32/21391/summary.html
COMMIT: 5120c82
CMSSW: CMSSW_12_3_X_2021-12-18-1100/slc7_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/36408/21391/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d73f32/21391/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d73f32/21391/git-merge-result

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 43
  • DQMHistoTests: Total histograms compared: 3461688
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3461666
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 42 files compared)
  • Checked 181 log files, 42 edm output root files, 43 DQM output files
  • TriggerResults: no differences found

@tvami
Copy link
Contributor Author

tvami commented Dec 19, 2021

+alca

  • finally we see what's expected: no changes at all

@cecilecaillol
Copy link
Contributor

+l1

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

@tvami
Copy link
Contributor Author

tvami commented Dec 20, 2021

Hi @perrotta @qliphy this doesnt actually require the external PR, please feel to merge it any time. Thanks!

@perrotta
Copy link
Contributor

@tvami which are the unit tests that were failing? And which is the unit test to look at in order to get assurance that the new tags are correctly picked up?

@tvami
Copy link
Contributor Author

tvami commented Dec 20, 2021

Hi @perrotta the unit test failure comes from outside of this PR, that is due to some geometry changes.

The orignal PR #35554 has failed both the addOnTests and several RelVal workflows. By adding the condition to the GT all of that is resolved. You can be assured that it's correct by seeing that there are no diffs in the RelVal comparisons (in any of them)

Speaking of the original PR, when merging this, can you please close #35554 ?

@perrotta
Copy link
Contributor

@tvami I read in the PR description "This tag is for testing purposes, thus it should be fed to the code via a test python cfg file and not hardcoded in the cpp code nor really read from the GT".
I wonder where is that "python config" which can test the newly inserted tags? Or do you plan to let them unattended, and have them tested at the first occasion anyone needs them?

@tvami
Copy link
Contributor Author

tvami commented Dec 20, 2021

@perrotta the issue is that this "testing purposes tag" has been in CMSSW from forever... (specifically from 9_2_X) and it was read directly from the DB instead of reading it from the GT. This is not allowed, and this is what #27393 is about. Now I first tried to get rid of this fully, and deleted all the code that reference the flag that switches this test tag usage on... Having very little knowledge of the L1T code, this lead to a segfault. So I went to the alternative no-op solution to feed the tag through the GT.

As for the longer term, the L1T experts should rewrite the code so there is a test python config that ESPrefers this tag if it's really needed, or just get rid of it all if it's not needed. Then we can remove it from the GT too. So what you see in this PR is a solution to a problem that can be done from the AlCa point of view. Everything else would need the L1T experts knowledge. Since #35554 has not converged in the last 2 month, I did this PR.

@perrotta
Copy link
Contributor

+1

  • Take conditions from the GT instead of hardcoding the tag in L1Trigger/L1TCalorimeter/python/simDigis_cff.py
  • @cms-sw/alca-l2 and @cms-sw/l1-l2 will take care of adapting the code in order to get rid of the tag if not needed

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.

Developers overriding production location for retrieving conditions in configurations
6 participants