-
Notifications
You must be signed in to change notification settings - Fork 249
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 labeling for tracking #1916
Conversation
A new Pull Request was created by @slava77 (Slava Krutelyov) for branch master. @cmsbuild, @smuzaffar, @aandvalenzuela, @iarspider can you please review it and eventually sign? Thanks. |
Pull request #1916 was updated. |
does it mean they will get labelled automatically? |
categories_map.py
Outdated
"RecoTracker", | ||
"RecoVertex", | ||
"TrackPropagation", | ||
"TrackingTools" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we need also RecoPixelVZero
and RecoVZero
(do not exist anymore since a long time).
Do we need to flag also non reconstruction packages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to flag also non reconstruction packages?
good point, here is more that matches
- CUDADataFormats/Vertex
- DataFormats/VertexReco
- DQM/Tracking
- Validation/RecoPixelVertexing
- Validation/RecoTrack
- Validation/RecoVertex
- Validation/Tracking
- FastSimulation/Tracking
- Geometry/GlobalTracking
what else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we need also
RecoPixelVZero
andRecoVZero
(do not exist anymore since a long time).
these were apparently removed in 9_2_X ( cms-sw/cmssw#18623) 10_0_X (cms-sw/cmssw#21456), respectively
But I guess I can add these as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add:
- CondFormats/BeamSpotObjects
- AnalysisDataFormats/TrackInfo
- CondCore/BeamSpotPlugins
- CondFormats/BeamSpotObjects
- CondTools/BeamSpot
- DQM/BeamMonitor
- Validation/TrackingMCTruth (already covered above)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add:
now in f2c36cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually in 9d8c766
Pull request #1916 was updated. |
yes |
…ginning of the name
Pull request #1916 was updated. |
looks good to me! |
there is tracking related code in |
right, I don't think there is a way to tag by individual files. |
files information is available and we can use that for these labels. |
doing a survey down to the file level now would be extremely tedious. I would suggest to continue incorporating files in the list once concrete requests materialize. What do you think? |
would this work already, or does it need some updates in the bot? |
No, it needs changes in bot code. |
@slava77 , should I update bot to do the matching against the changed file ? |
I think that we can merge this PR first and then benefit from the file-level selection when it is available. |
this has been merged and bot properly added the label for cms-sw/cmssw#30373 |
add packages and subsystems to be labeled for tracking
@mmusich
do you have any comments?