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
add PV monitoring @HLT #17996
add PV monitoring @HLT #17996
Conversation
fix bug fix add ndof add PV monitoring@HLT for online DQM
fix VALIDATION step in workflows w/ HLT:@Fake fix fix fix DQM step as well !
fix add PAGs client fix fix handling of condDataValidation fix HARVESTING step in run1 no HLT Validation HARVESTING and no HLT DQM HARVESTING
A new Pull Request was created by @mtosi (mia tosi) for master. It involves the following packages: Configuration/PyReleaseValidation @perrotta, @cmsbuild, @civanch, @dmitrijus, @silviodonato, @fwyzard, @mdhildreth, @fabozzi, @Martin-Grunewald, @franzoni, @kpedro88, @slava77, @GurpreetSinghChahal, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
+1 |
+1 |
+1 |
+1 |
Looks like this PR creates problems:
|
Or this one:
|
It affects PRef and PIon (and the Fake*) HLT menus, which probably do not contain the module. |
yes, I was just seeing the same thing - will revert for now while this can be fixed.
… On Mar 22, 2017, at 8:52 AM, Martin Grunewald ***@***.***> wrote:
Or this one:
----- Begin Fatal Exception 22-Mar-2017 08:16:50 CET-----------------------
An exception of category 'ProductNotFound' occurred while
[0] Processing Event run: 1 lumi: 3 event: 103
[1] Running path 'dqmofflineOnPAT_step'
[2] Calling method for module PrimaryVertexMonitor/'hltVerticesPFFilterMonit\
oring'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: std::vector<reco::Vertex>
Looking for module label: hltVerticesPFFilter
Looking for productInstanceName:
Additional Info:
[a] If you wish to continue processing events after a ProductNotFound exc\
eption,
add "SkipEvent = cms.untracked.vstring('ProductNotFound')" to the "options" PSe\
t in the configuration.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 22-Mar-2017 08:16:50 CET-----------------------
An exception of category 'ProductNotFound' occurred while
[0] Processing Event run: 1 lumi: 3 event: 102
[1] Running path 'dqmofflineOnPAT_step'
[2] Calling method for module PrimaryVertexMonitor/'hltVerticesPFFilterMonit\
oring'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: std::vector<reco::Vertex>
Looking for module label: hltVerticesPFFilter
Looking for productInstanceName:
Additional Info:
[a] If you wish to continue processing events after a ProductNotFound exc\
eption,
add "SkipEvent = cms.untracked.vstring('ProductNotFound')" to the "options" PSe\
t in the configuration.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
opsi |
I'm confused :(
I'm in the branch
under
|
maybe your branch is not in a consistent state? You can try
CMSSW_9_1_X_2017-03-21-2300 (not working in our tests, your PR in)
CMSSW_9_1_X_2017-03-22-1100 (working in our tests, your PR out)
… On Mar 22, 2017, at 1:56 PM, mia tosi ***@***.***> wrote:
I'm confused :(
I ran
runTheMatrix.py -l 134.805 &
and I have
134.805_RunMET2015C+RunMET2015C+HLTDR2_25ns+RECODR2_25nsreHLT_HIPM+HARVESTDR2 Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED - time date Wed Mar 22 13:28:42 2017-date Wed Mar 22 13:05:20 2017; exit: 0 0 0 0
1 1 1 1 tests passed, 0 0 0 0 failed
I'm in the branch
git branch
CMSSW_9_1_X
backport-attempt
backport-from-CMSSW_9_0_X
from-CMSSW_9_1_X_2017-03-20-1100
* ***@***.***_91x
under
echo $CMSSW_BASE/
/afs/cern.ch/work/t/tosi/public/trackingHLT/DQM/cleanAREA/CMSSW_9_1_X_2017-03-20-1100/
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@wddgit Could be an interaction with the Task pull request. |
it didn't seem likely to me. but maybe you can confirm if there is a potential conflict
… On Mar 22, 2017, at 3:11 PM, Chris Jones ***@***.***> wrote:
@wddgit Could be an interaction with the Task pull request.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Just quickly skimming this PR, I cannot see anything I would expect to interact badly with the Tasks PR. At this point, I think the Tasks PR is unrelated to these failures. If you find more evidence pointing in that direction, ask and I will take a closer look. This problem did start at the same point in time and the Tasks PR modifies a lot of the code that processes the python configurations so it reasonable to suspect it. On the hand, the Tasks PR mostly effects which modules are configured to run in unscheduled mode. It should not affect things that are put on Paths or EndPaths and it looks like the content in this PR is all on Paths or EndPaths. |
I've just done
but I get
what should I do ? |
I think the problem you are encountering is the fact that the pull request was merged (and then reverted) and therefore git sees no reason to merge it again. Maybe it would be better to try to do a 'rebase' of your original branch onto the master branch |
forward port of PR #17667
and
fix of PR #17693, which have some issues w/ merging