Pr 20494 plus l1stage1 alias #20518
Pr 20494 plus l1stage1 alias #20518
Conversation
|
The code-checks are being triggered in jenkins. |
|
please test |
|
+code-checks |
|
The tests are being triggered in jenkins. |
|
A new Pull Request was created by @rekovic for master. It involves the following packages: Configuration/AlCa @ghellwig, @cmsbuild, @silviodonato, @arunhep, @cerminar, @Martin-Grunewald, @franzoni, @fwyzard, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
-1 Tested at: c30cba8 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: AddOn
I found errors in the following addon tests: cmsDriver.py TTbar_13TeV_TuneCUETP8M1_cfi --conditions auto:run2_mc --fast -n 100 --eventcontent AODSIM,DQM --relval 100000,1000 -s GEN,SIM,RECOBEFMIX,DIGI:pdigi_valid,L1,DIGI2RAW,L1Reco,RECO,EI,VALIDATION --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --datatier GEN-SIM-DIGI-RECO,DQMIO --beamspot NominalCollision2015 --era Run2_25ns : FAILED - time: date Thu Sep 14 21:09:12 2017-date Thu Sep 14 21:00:40 2017 s - exit: 16640 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
Looks like the |
|
maybe its time to re-discuss how to manage GTs across years as the detector is slowly upgraded and improved? (as it seems the agreed solution years ago has been abandoned before commissioned)
… On Sep 15, 2017, at 1:20 PM, Arun Kumar ***@***.***> wrote:
@arunhep commented on this pull request.
In Configuration/AlCa/python/autoCond.py:
> #GlobalTag for MC production with optimistic alignment and calibrations for Run2
- 'run2_mc' : '93X_mcRun2_asymptotic_v1',
+ 'run2_mc' : '93X_mcRun2_asymptotic_v2',
+ # GlobalTag for MC production (L1 Trigger Stage1) with starup-like alignment and calibrations for Run2, L1 trigger in Stage1 mode
+ 'run2_mc_l1stage1' : '93X_mcRun2_asymptotic_v1',
@rekovic @Martin-Grunewald we can not support an extra key to support the stage1 and stage 2 separately because this costs us a lot as we have to maintain another queue with stage 1 configurations. There must be another way out.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I am not aware of any strategy which was discussed in past. And yes we are ready to discuss again. |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
+1 (even if l1 not required) |
|
+1 |
|
Comparison is ready Comparison Summary:
|
|
+1 |
|
@davidlange6, @Dr15Jones, @smuzaffar, can you please sign or comment. |
|
+1 |
cmsbuild
added
core-approved
fully-signed
and removed
core-pending
pending-signatures
labels
|
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) |
|
@davidlange6 we have few other updates lined up so please merge this PR at your earliest convenience. |
|
+1 |
This PR 20494 plus changes in configuration aliases needed for l1 stage1.
It introduces a new alias
run2_mc_l1stage1and adjusts the configuration of HLT that is used by the AddOn tests, to pick up this new alias.PR 20494: 'run2_mc'was updated to '93X_mcRun2_asymptotic_v2', which is what we want for Stage2.
For Stage1, we keep '93X_mcRun2_asymptotic**_v1**' as it have conditions relevant for 2015.