Build CMSSW_12_1_0_pre3

[qliphy]

No description provided.

[cmsbuild]

Request received. I will start to build the release after one of the following approve the issue: @perrotta, @smuzaffar, @qliphy, @dpiparo. You can do this by writing "+1" in a comment.
You can also ask me to begin to build cmssw-tool-conf first ( Cannot be done for patch releases ). To do this write "build cmssw-tool-conf" in a comment. I will start to build cmssw-tool-conf and then wait for the "+1" to start the build of the release.
CMSSW Branch: CMSSW_12_1_X(master)
Architecture: slc7_amd64_gcc900(Production), slc7_amd64_gcc10, slc7_aarch64_gcc9, slc7_ppc64le_gcc9, cc8_amd64_gcc9, cc8_aarch64_gcc9, cc8_ppc64le_gcc9

[qliphy]

+1

[cmsbuild]

Release created: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_12_1_0_pre3. The tag was created on top of branch: https://github.com/cms-sw/cmssw/tree/master

[cmsbuild]

Queuing Jenkins build for the following architectures: cc8_amd64_gcc9, cc8_aarch64_gcc9, slc7_aarch64_gcc9, cc8_ppc64le_gcc9, slc7_amd64_gcc10, slc7_amd64_gcc900, slc7_ppc64le_gcc9
You can abort the build by writing "Abort" in a comment. I will delete the release, the cmssw and cmsdist tag, and close the issue. You can't abort the upload once at least one achitecture is being uploaded.
If you are building cmssw-tool-conf first, I will wait for each architecture to finish to start the build of cmssw.

[cmsbuild]

The build has started for cc8_amd64_gcc9 in cmsbuild19.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/3175/console
CMSDIST Branch: IB/CMSSW_12_1_X/cc8, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The build has started for slc7_amd64_gcc900 in cmsbuild03.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/3177/console
CMSDIST Branch: IB/CMSSW_12_1_X/master, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The build has started for slc7_amd64_gcc10 in cmsbuild11.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/3176/console
CMSDIST Branch: IB/CMSSW_12_1_X/gcc10, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The build has started for cc8_aarch64_gcc9 in techlab-arm64-01-thunderx2-02a.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/3178/console
CMSDIST Branch: IB/CMSSW_12_1_X/cc8, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The build has started for slc7_aarch64_gcc9 in techlab-arm64-01-thunderx2-02b.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/3180/console
CMSDIST Branch: IB/CMSSW_12_1_X/master, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The build has started for cc8_ppc64le_gcc9 in ibmminsky-2b.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/3179/console
CMSDIST Branch: IB/CMSSW_12_1_X/cc8, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The tests have finished for slc7_ppc64le_gcc9
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-slc7_ppc64le_gcc9/3181

Tests results:
39 38 37 28 18 4 1 1 1 tests passed, 0 0 0 0 0 0 0 0 0 failed

[cmsbuild]

The tests have finished for slc7_aarch64_gcc9
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-slc7_aarch64_gcc9/3180

Tests results:
39 38 37 28 18 4 1 1 1 tests passed, 0 0 0 0 0 0 0 0 0 failed

[cmsbuild]

The was an error for slc7_amd64_gcc10.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-slc7_amd64_gcc10/3176

[qliphy]

@smuzaffar @makortel There is a build error for slc7_amd64_gcc10, as reported by @perrotta in
#35240 (comment)
Do you have any idea on this? Or if there is NO plan for gcc10 validation, can we go ahead with this build of 12_1_0_pre3? Thanks!
Adding also @bsunanda （a fix provided now in https://github.com/cms-sw/cmssw/pull/35282）

https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-slc7_amd64_gcc10/3176/LOGS/cms/cmssw/CMSSW_12_1_0_pre3/log
/data/cmsbld/jenkins/workspace/auto-builds/CMSSW_12_1_0_pre3-slc7_amd64_gcc10/build/CMSSW_12_1_0_pre3-build/slc7_amd64_gcc10/external/gcc/10.3.0/bin/../lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../../x86_64-unknown-linux-gnu/bin/ld: tmp/slc7_amd64_gcc10/src/Calibration/HcalCalibAlgos/plugins/CalibrationHcalCalibAlgosPlugins/HOCalibAnalyzer.cc.o: in function HOCalibAnalyzer::HOCalibAnalyzer(edm::ParameterSet const&)': HOCalibAnalyzer.cc:(.text+0x598d): undefined reference to HOCalibAnalyzer::nphimx'
/data/cmsbld/jenkins/workspace/auto-builds/CMSSW_12_1_0_pre3-slc7_amd64_gcc10/build/CMSSW_12_1_0_pre3-build/slc7_amd64_gcc10/external/gcc/10.3.0/bin/../lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../../x86_64-unknown-linux-gnu/bin/ld: tmp/slc7_amd64_gcc10/src/Calibration/HcalCalibAlgos/plugins/CalibrationHcalCalibAlgosPlugins/HOCalibAnalyzer.cc.o: in function HOCalibAnalyzer::HOCalibAnalyzer(edm::ParameterSet const&)': HOCalibAnalyzer.cc:(.text+0x739d): undefined reference to HOCalibAnalyzer::nphimx'
collect2: error: ld returned 1 exit status
gmake: *** [tmp/slc7_amd64_gcc10/src/Calibration/HcalCalibAlgos/plugins/CalibrationHcalCalibAlgosPlugins/libCalibrationHcalCalibAlgosPlugins.so] Error 1
Entering library rule at Calibration/HcalCalibAlgos

[cmsbuild]

The build has finished sucessfully for the architecture cc8_ppc64le_gcc9 and is ready to be uploaded.
You can start the uploads by writing the comment: "upload all". I will upload all the architectures as soon as the build finishes successfully.
You can see the log for the build here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-cc8_ppc64le_gcc9/3179
Some tests ( runTheMatrix.py -s ) are being run, the results will be posted when done.

[cmsbuild]

The build has finished sucessfully for the architecture slc7_amd64_gcc900 and is ready to be uploaded.
You can start the uploads by writing the comment: "upload all". I will upload all the architectures as soon as the build finishes successfully.
You can see the log for the build here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-slc7_amd64_gcc900/3177
Some tests ( runTheMatrix.py -s ) are being run, the results will be posted when done.

[cmsbuild]

The tests have finished for cc8_ppc64le_gcc9
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-cc8_ppc64le_gcc9/3179

Tests results:
37 34 14 4 3 0 0 0 0 tests passed, 2 2 20 2 0 0 0 0 0 failed

[cmsbuild]

The build has finished sucessfully for the architecture cc8_amd64_gcc9 and is ready to be uploaded.
You can start the uploads by writing the comment: "upload all". I will upload all the architectures as soon as the build finishes successfully.
You can see the log for the build here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-cc8_amd64_gcc9/3175
Some tests ( runTheMatrix.py -s ) are being run, the results will be posted when done.

[cmsbuild]

The tests have finished for slc7_amd64_gcc900
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-slc7_amd64_gcc900/3177

Tests results:
39 38 37 28 18 4 1 1 1 tests passed, 0 0 0 0 0 0 0 0 0 failed

[cmsbuild]

The tests have finished for cc8_amd64_gcc9
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-cc8_amd64_gcc9/3175

Tests results:
39 38 37 28 18 4 1 1 1 tests passed, 0 0 0 0 0 0 0 0 0 failed

[makortel]

Or if there is NO plan for gcc10 validation, can we go ahead with this build of 12_1_0_pre3?

I'd think that since there has been no specific fix for the reported discrepancy in GEM plots (that seem more like red herring caused by non-gaussian fluctuations), strictly speaking we would not need a new validation campaign for gcc10. A counter-argument would be that lot's of other developments have been merged in between that have not been validated for gcc10. Counter-counter-argument would be that gcc10 will be implicitly re-validated when we switch to it for production.

[qliphy]

abort

[qliphy]

Or if there is NO plan for gcc10 validation, can we go ahead with this build of 12_1_0_pre3?

I'd think that since there has been no specific fix for the reported discrepancy in GEM plots (that seem more like red herring caused by non-gaussian fluctuations), strictly speaking we would not need a new validation campaign for gcc10. A counter-argument would be that lot's of other developments have been merged in between that have not been validated for gcc10. Counter-counter-argument would be that gcc10 will be implicitly re-validated when we switch to it for production.

Thanks @makortel
Now a fix has been merged #35282
Let's rebuild pre3.

[cmsbuild]

Deleting CMSSW_12_1_0_pre3:

• Release successfully deleted

• cmssw tag CMSSW_12_1_0_pre3 successfully deleted.

• cmsdist tag REL/CMSSW_12_1_0_pre3/slc7_amd64_gcc900 successfully deleted.

• I was not able to delete the tag REL/CMSSW_12_1_0_pre3/slc7_amd64_gcc10. Probaly it had not been created.

• cmsdist tag REL/CMSSW_12_1_0_pre3/slc7_aarch64_gcc9 successfully deleted.

• cmsdist tag REL/CMSSW_12_1_0_pre3/slc7_ppc64le_gcc9 successfully deleted.

• cmsdist tag REL/CMSSW_12_1_0_pre3/cc8_amd64_gcc9 successfully deleted.

• I was not able to delete the tag REL/CMSSW_12_1_0_pre3/cc8_aarch64_gcc9. Probaly it had not been created.

• cmsdist tag REL/CMSSW_12_1_0_pre3/cc8_ppc64le_gcc9 successfully deleted.

You must create a new issue to start over the build.

[cmsbuild]

The was an error for cc8_aarch64_gcc9.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_12_1_0_pre3-cc8_aarch64_gcc9/3178

[makortel]

Now a fix has been merged #35282
Let's rebuild pre3.

That works of course too :)