GT Updates with GEM electronics map, hadronic PF calibrations, JECs for 2017 MC #22642
Conversation
|
The code-checks are being triggered in jenkins. |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22642/3992 |
|
A new Pull Request was created by @arunhep (Arun Kumar) for master. It involves the following packages: Configuration/AlCa @ghellwig, @arunhep, @cerminar, @cmsbuild, @franzoni, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@cmsbuild please test |
|
The tests are being triggered in jenkins. |
|
-1 Tested at: e37ad82 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: Build
I found an error when building: >> Compiling python modules src/DQM/SiStripMonitorCluster/python >> Done generating edm plugin poisoned information >> All python modules compiled >> Plugins of all types refreshed. gmake[1]: Leaving directory '/build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_1_X_2018-03-14-2300' gmake: *** [There are compilation/build errors. Please see the detail log above.] Error 1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison not run due to Build errors (RelVals and Igprof tests were also skipped) |
cmsbuild
added
comparison-notrun
tests-rejected
and removed
comparison-pending
tests-started
labels
|
the build errors are unrelated to this PR. |
|
@cmsbuild please test |
|
The code-checks are being triggered in jenkins. |
|
@perrotta |
|
@cmsbuild please test |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22642/4013 |
|
The tests are being triggered in jenkins. |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
+1 |
|
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, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
cmsbuild
added
alca-approved
fully-signed
and removed
alca-pending
pending-signatures
labels
|
@arunhep I notice in the comparison differences in Run1 workflows, these are justified by the updates there I assume. This PR also includes all the updates inserted in 9_4_MAOD_X, right? |
yes because PF hadronic calibration updates also entered in Run1 workflows. |
|
+1 |
Summary of changes in Global Tags
RunI simulation
RunI Heavy Ions scenario : 101X_mcRun1_HeavyIon_v2 as 101X_mcRun1_HeavyIon_v1 with the following changes:
RunI Ideal scenario : 101X_mcRun1_design_v2 as 101X_mcRun1_design_v1 with the following changes:
RunI Proton-Lead scenario : 101X_mcRun1_pA_v2 as 101X_mcRun1_pA_v1 with the following changes:
RunI Realistic scenario : 101X_mcRun1_realistic_v2 as 101X_mcRun1_realistic_v1 with the following changes:
RunII simulation
RunII Asymptotic scenario : 101X_mcRun2_asymptotic_v3 as 101X_mcRun2_asymptotic_v2 with the following changes:
RunII CRAFT scenario : 101X_mcRun2cosmics_startup_deco_v3 as 101X_mcRun2cosmics_startup_deco_v2 with the following changes:
RunII Heavy Ions scenario : 101X_mcRun2_HeavyIon_v4 as 101X_mcRun2_HeavyIon_v3 with the following changes:
RunII Ideal scenario : 101X_mcRun2_design_v3 as 101X_mcRun2_design_v2 with the following changes:
RunII Proton-Lead scenario : 101X_mcRun2_pA_v3 as 101X_mcRun2_pA_v2 with the following changes:
RunII Startup scenario : 101X_mcRun2_startup_v3 as 101X_mcRun2_startup_v2 with the following changes:
RunI data
RunI HLT processing : 101X_dataRun2_HLT_frozen_v5 as 101X_dataRun2_HLT_frozen_v4 with the following changes:
RunI Offline processing : 101X_dataRun2_v7 as 101X_dataRun2_v6 with the following changes:
RunII data
RunII HLTHI processing : 101X_dataRun2_HLTHI_frozen_v6 as 101X_dataRun2_HLTHI_frozen_v5 with the following changes:
RunII HLT relval processing : 101X_dataRun2_HLT_relval_v6 as 101X_dataRun2_HLT_relval_v5 with the following changes:
RunII Offline processing : 101X_dataRun2_v7 as 101X_dataRun2_v6 with the following changes:
RunII Offline relval processing : 101X_dataRun2_relval_v7 as 101X_dataRun2_relval_v6 with the following changes:
RunII Prompt processing : 101X_dataRun2_PromptLike_v7 as 101X_dataRun2_PromptLike_v6 with the following changes:
RunI HLT processing : 101X_dataRun2_HLT_frozen_v5 as 101X_dataRun2_HLT_frozen_v4 with the following changes:
Upgrade
PhaseII realistic scenario : 101X_upgrade2023_realistic_v3 as 101X_upgrade2023_realistic_v2 with the following changes:
PhaseI 2018 cosmics scenario : 101X_upgrade2018cosmics_realistic_deco_v5 as 101X_upgrade2018cosmics_realistic_deco_v4 with the following changes:
PhaseI 2018 design scenario : 101X_upgrade2018_design_v5 as 101X_upgrade2018_design_v4 with the following changes:
PhaseI 2018 realistic scenario : 101X_upgrade2018_realistic_v4 as 101X_upgrade2018_realistic_v3 with the following changes:
PostLS2 design scenario : 101X_postLS2_design_v3 as 101X_postLS2_design_v2 with the following changes:
PostLS2 realistic scenario : 101X_postLS2_realistic_v3 as 101X_postLS2_realistic_v2 with the following changes:
2017_MC
PhaseI 2017 cosmics peak scenario : 101X_mc2017cosmics_realistic_peak_v5 as 101X_mc2017cosmics_realistic_peak_v4 with the following changes:
PhaseI 2017 cosmics scenario : 101X_mc2017cosmics_realistic_deco_v5 as 101X_mc2017cosmics_realistic_deco_v4 with the following changes:
PhaseI 2017 design scenario : 101X_mc2017_design_IdealBS_v5 as 101X_mc2017_design_IdealBS_v4 with the following changes:
PhaseI 2017 realistic scenario : 101X_mc2017_realistic_v5 as 101X_mc2017_realistic_v4 with the following changes: