Advance to latest release of RecoBTag/CTagging data.

[ghost]

cms-data/RecoBTag-CTagging@7a5db41

[cmsbuild]

A new Pull Request was created by @Degano (Alessandro Degano) for branch IB/CMSSW_8_0_X/stable.

@cmsbuild, @smuzaffar, @Degano, @iahmad-khan, @davidlange6 can you please review it and eventually sign? Thanks.
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.

[ghost]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/cmsdist-test-pr/73/console

[slava77]

@Degano
I'm looking at https://cmssdt.cern.ch/jenkins/job/cmsdist-test-pr/73/console
It looks like the full release is recompiled.
This is excessive for data externals.

Is the logic for testing to have a full rebuild for any cmsdist update?
We maybe need to get some improvement to this.

In this case we only needed the new external built and then the matrix&addOn tests rerun.

[cmsbuild]

-1

Tested at: 8bc27c9
I found errors in the following unit tests:

---> test runtestSimCalorimetryHGCalSimProducers had ERRORS
---> test runtestRecoLocalCaloHGCalRecProducers had ERRORS

you can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2106/73/summary.html

[slava77]

the unit test failures are unrelated, they are present in the IB as well
https://cmssdt.cern.ch/SDT/cgi-bin/buildlogs/slc6_amd64_gcc493/CMSSW_8_0_X_2016-01-27-2300/unitTestLogs/RecoLocalCalo/HGCalRecProducers

looking at https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2106/73/summary.html
even after 11 hours, the comparisons have never completed.

from the change in the code
cms-data/RecoBTag-CTagging@V01-00-00...V01-00-02
it's is clear that only new files are added.
I think at this point it is more important to merge this and have the new training files in the release.
If they are good, we can get the cms-sw/cmssw#13054 in as well.
The last set of tests check only the jenkins test infrastructure, not very successfully.

[ghost]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/cmsdist-test-pr/80/console

[cmsbuild]

+1
Tested at: 8bc27c9
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2106/80/summary.html

[slava77]

@Degano
which jenkins project is running the comparisons for builds done in cmsdist-test-pr?
The status for this test https://cmssdt.cern.ch/jenkins/job/cmsdist-test-pr/80/ says there is supposed to be a subproject job in https://cmssdt.cern.ch/jenkins/job/compare-root-files-short-matrix/, but I do not see anything relevan there.

Please clarify where to look for the comparison job.
Thank you.

[smoortga]

Dear @Degano, Dear @slava77,
Since the dealine for the last open 8.0.X. release is only two days away, I was wondering if you could update @mverzett and myself about the status of our PR. It seems like all of the tests discribed above have eventually passed successfully (or is this not the case?), and our cmssw PR (cms-sw/cmssw#13054) is still waiting for this one to be approved.

Thanks a lot!
Cheers, Seth

[slava77]

@davidlange6
This is just to note that we may need some extra time (or action) to get #13054 through into 80X (once this external update is done).

[davidlange6]

I'll merge it - but yes, any externals update means a full cmssw rebuild.

[slava77]

On 1/30/16 10:58 AM, David Lange wrote:

I'll merge it - but yes, any externals update means a full cmssw rebuild.

Thank you for the merge.
I suppose, the file will show up in the -2300 IB.

The case of data file externals may better be reconsidered.
Although a better way is still to push everything to a GT.
At an extreme, when only this external is changing,
a sub-MB size update in a data file costs a few GB of release space.

—
Reply to this email directly or view it on GitHub
#2106 (comment).