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
Clean up errors reported by static analyzer #1222
Clean up errors reported by static analyzer #1222
Conversation
ianna
commented
Oct 29, 2013
- Clean up errors reported by static analyzer
- Fix configurations to run on auto conditions
… run on auto conditions
A new Pull Request was created by @ianna for CMSSW_7_0_X. Clean up errors reported by static analyzer It involves the following packages: Geometry/DTGeometry @smuzaffar, @civanch, @Dr15Jones, @ianna, @mdhildreth, @nclopezo, @ktf can you please review it and eventually sign? Thanks. |
@ianna, any reason why you did not sign it for geometry? |
+1 |
This pull request is fully signed and it will be integrated in one of the next IBs unless changes or unless it breaks tests. @ktf can you please take care of it? |
Misc Geometry fixes -- statics in Geometry/DTGeometry, use auto conditions
@@ -4,7 +4,9 @@ | |||
process.load("Configuration.StandardSequences.GeometryDB_cff") | |||
process.load("CondCore.DBCommon.CondDBSetup_cfi") | |||
process.load('Configuration.StandardSequences.FrontierConditions_GlobalTag_cff') | |||
process.GlobalTag.globaltag = 'MC_31X_V8::All' | |||
from Configuration.AlCa.autoCond import autoCond |
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.
In general you should use two different pull requests for logically orthogonal changes.