Build CMSSW_15_0_0

[mandrenguyen]

No description provided.

[cmsbuild]

Request received. I will start to build the release after one of the following approve the issue: @smuzaffar, @sextonkennedy, @rappoccio, @antoniovilela, @mandrenguyen. 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_15_0_X
Architecture: el8_amd64_gcc12(Production), el9_amd64_gcc12, el9_aarch64_gcc12, el8_aarch64_gcc12, el8_amd64_gcc13

[mandrenguyen]

+1

[cmsbuild]

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

[cmsbuild]

Queuing Jenkins build for the following architectures: el9_amd64_gcc12, el8_aarch64_gcc12, el8_amd64_gcc12, el9_aarch64_gcc12, el8_amd64_gcc13
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 architecture 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 el8_amd64_gcc12 in cmsbuild958.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4816/console
CMSDIST Branch: IB/CMSSW_15_0_X/master, PKGTOOLS Branch: V00-34-XX

[cmsbuild]

The build has started for el8_amd64_gcc13 in cmsbuild959.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4817/console
CMSDIST Branch: IB/CMSSW_15_0_X/g13, PKGTOOLS Branch: V00-34-XX

[cmsbuild]

The build has started for el8_aarch64_gcc12 in arm-vocms-01a.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4819/console
CMSDIST Branch: IB/CMSSW_15_0_X/master, PKGTOOLS Branch: V00-34-XX

[cmsbuild]

The build has started for el9_amd64_gcc12 in cmsbuild957.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4818/console
CMSDIST Branch: IB/CMSSW_15_0_X/cs9, PKGTOOLS Branch: V00-34-XX

[cmsbuild]

The build has started for el9_aarch64_gcc12 in arm-vocms-01b.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4820/console
CMSDIST Branch: IB/CMSSW_15_0_X/cs9, PKGTOOLS Branch: V00-34-XX

[cmsbuild]

The build has finished successfully for the architecture el9_aarch64_gcc12 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_15_0_0-el9_aarch64_gcc12/4820
Some tests ( runTheMatrix.py -s ) are being run, the results will be posted when done.

[cmsbuild]

Generating release notes since CMSSW_15_0_0_pre3.
You can see the progress here:
https://cmssdt.cern.ch/jenkins/job/release-produce-changelog/
I will generate an announcement template.

[cmsbuild]

You can use this template for announcing the release:

Hi all,

The production release CMSSW_15_0_0 is now available for the following architectures:

el8_amd64_gcc12 (production)
el9_aarch64_gcc12
el9_amd64_gcc12
el8_amd64_gcc13
el8_aarch64_gcc12

The release notes of what changed with respect to CMSSW_15_0_0_pre3 can be found at:

https://github.com/cms-sw/cmssw/releases/CMSSW_15_0_0

Cheers,
cms-bot

You can also click here to send the email.

[cmsbuild]

The release notes are ready: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_15_0_0

[jfernan2]

@jfernan2 is this increased memory consumption something we can spot on your profiling

Yes, I was waiting for the pre3 and 15_0_0 processing by the Core RECO team, but in pre1 and pre2 was already when compared to 14_2_0, though not so large w.r.t. 14_2_0_pre1/2/3

https://cms-reco-profiling.web.cern.ch/cms-reco-profiling/results/summary_plot_html/CMSSW_14_2_step3_29834.21.html
https://cms-reco-profiling.web.cern.ch/cms-reco-profiling/results/summary_plot_html/CMSSW_15_0_step3_29834.21.html

More over, the thing depends much on th wf number considered:

https://cms-reco-profiling.web.cern.ch/cms-reco-profiling/results/summary_plot_html/CMSSW_14_2_step3_25034.21.html
https://cms-reco-profiling.web.cern.ch/cms-reco-profiling/results/summary_plot_html/CMSSW_15_0_step3_25034.21.html

It is known that RSS is not a good memory proxy

[cmsbuild]

The cleanup has started for el8_amd64_gcc12

[cmsbuild]

The cleanup has started for el9_amd64_gcc12

[cmsbuild]

The cleanup has started for el9_aarch64_gcc12

[cmsbuild]

The cleanup has started for el8_aarch64_gcc12

[cmsbuild]

The cleanup has started for el8_amd64_gcc13

[cmsbuild]

The workspace for el8_aarch64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_15_0_0-el8_aarch64_gcc12/3231

[cmsbuild]

The workspace for el8_amd64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_15_0_0-el8_amd64_gcc12/3232

[cmsbuild]

The workspace for el9_aarch64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_15_0_0-el9_aarch64_gcc12/3234

[cmsbuild]

The workspace for el8_amd64_gcc13 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_15_0_0-el8_amd64_gcc13/3233

[cmsbuild]

The workspace for el9_amd64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_15_0_0-el9_amd64_gcc12/3235