Skip to content
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

62XSLHC - fix metUncertaintyTools for scheduled processing #3932

Conversation

vadler
Copy link

@vadler vadler commented May 19, 2014

Backport of #3929

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @vadler (Volker Adler) for CMSSW_6_2_X_SLHC.

62XSLHC - fix metUncertaintyTools for scheduled processing

It involves the following packages:

PhysicsTools/PatUtils

@nclopezo, @vadler, @cmsbuild, @Degano, @monttj can you please review it and eventually sign? Thanks.
@TaiSakuma, @nhanvtran this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
@andersonjacob, @mark-grimes you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@andersonjacob
Copy link
Contributor

merge

passing tests: 10000,10200,10400,11200,11400,12000,12800,13000,13600,14600
failing tests: 12200 Step2-FAILED code 34304,12400 Step2-FAILED code 34304,12600 Step1-FAILED code 34304,13800 Step2-FAILED code 34304,14000 Step2-FAILED code 34304,14200 Step2-FAILED code 34304,14400 Step2-FAILED code 34304

cmsbuild added a commit that referenced this pull request May 19, 2014
…heduled

62XSLHC - fix `metUncertaintyTools` for scheduled processing
@cmsbuild cmsbuild merged commit a62344a into cms-sw:CMSSW_6_2_X_SLHC May 19, 2014
@vadler vadler deleted the 62XSLHC-fixMetUncertaintyToolsScheduled branch May 20, 2014 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants