guard against blank lines in db.txt which cause tlf2esd.txt report to not be generated.

[gartung]

No description provided.

[cmsbuild]

A new Pull Request was created by @gartung (Patrick Gartung) for CMSSW_7_2_X.

guard against blank lines in db.txt which cause tlf2esd.txt report to not be generated.

It involves the following packages:

Utilities/StaticAnalyzers

@cmsbuild, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks.
@wddgit 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.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[gartung]

@ktf @Dr15Jones This fixes the bug that caused this file to be empty
https://cmssdt.cern.ch/SDT/jenkins-artifacts/ib-static-analysis/CMSSW_7_3_X_2014-10-01-0200/slc6_amd64_gcc481/reports/tlf2esd.txt

[Dr15Jones]

+1
this is a bug fix

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes or unless it breaks tests. @nclopezo can you please take care of it?

[cmsbuild]

+1
Tested at: 6c2a5ab
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5637/1105/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine). @nclopezo can you please take care of it?

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5637/1105/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine). @nclopezo can you please take care of it?

[gartung]

@ktf What is this waiting on? Should I submit to CMSSW_7_3_X queue instead?

[Dr15Jones]

Since 7_2_X is closing, changes to 7_2_X now must be approved at a meeting held once a week on Tuesday. A seperate 7_3_X would get it into that release faster.

[ktf]

Indeed @Dr15Jones is right. For this particular case I guess we do not care, though. Please ping me explicitly whenever you have fixes for the static analyzer and I'll bypass the signatures.

[gartung]

@ktf Will this get ported to 73X?

[ktf]

not in the short term, since there is a few conflicts between 72X and 73X which need to be resolved first. I'd do a separate pull request.