Build CMSSW_10_6_41

[rappoccio]

Requested to add new PYTHIA BBL hook from #44419

[cmsbuild]

Request received. I will start to build the release after one of the following approve the issue: @sextonkennedy, @rappoccio, @antoniovilela, @smuzaffar. 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_10_6_X
Architecture: slc7_amd64_gcc700(Production)

[rappoccio]

+1

[cmsbuild]

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

[cmsbuild]

Queuing Jenkins build for the following architectures: slc7_amd64_gcc700
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 slc7_amd64_gcc700 in cmsbuild101.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4344/console
CMSDIST Branch: IB/CMSSW_10_6_X/gcc700, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

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

[antoniovilela]

@smuzaffar @cms-sw/orp-l2
Error when building external.
Probably not related, 10_6_X is now failing a unit test in IB.
Best to fix unit test before restarting build ?

[cmsbuild]

The cmssw-tool-conf build has started for slc7_amd64_gcc700 in cmsbuild115.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/4345/console
CMSDIST Branch: IB/CMSSW_10_6_X/gcc700, PKGTOOLS Branch: V00-33-XX

[cmsbuild]

The cmssw-tool-conf build has finished sucessfully for the architecture slc7_amd64_gcc700 and it was automatically uploaded.
Remember that if you write "+1" I will start to build this and all the architectures as soon as their cmssw-tool-conf finish.
You can see the log for the build here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_10_6_41-slc7_amd64_gcc700/4345

[antoniovilela]

@smuzaffar @cms-sw/orp-l2
Hi Shahzad, would it make sense to trigger another 10_6_X IB to see if the unit test error is persistent?
Can you see a correlation with the latest update?

[smuzaffar]

Although I have triggered an IB but this test is failing since a long time so it not related to any recent updates.

[antoniovilela]

Although I have triggered an IB but this test is failing since a long time so it not related to any recent updates.

Hi Shahzad, I do not seem to have access to this link.

[antoniovilela]

@smuzaffar
Hi Shahzad, from the IB page I only see a couple of IBs. How could I track down when the unit test started failing?
Do you think it is harmless?
Thanks.

[smuzaffar]

may be the link is only accessible within cern or you need to use your CERN SSO to login. The link only shows last 8 weeks of tests and this test is failing for all week. So can not tell when it start failing

[davidlange6]

the permissions appear to require something more than just CERN SSO w/ CMS permissions

[antoniovilela]

@smuzaffar
Concerning the link, this is the message: "Unauthorized to log in. A missing role is required to access this application. Please contact the application owner to get access."
Shahzad, do you know what this test is doing, what is the return value it is testing to be a certain value?
Trying to quickly run locally (scram b runtests) gives a segfault for this test.

[smuzaffar]

@antoniovilela , unit test itself runs fine when lcoally build/run [a]. Thsi test send kill signal 6 and 11 to check if it fails with the right exit code. Test if failing for IBs due the way bot runs it. #44706 should fix this unit test for IBs

[a]

Singularity> scram b unittests_testFWCoreSharedMemoryMonitorThreadSignals
>> Local Products Rules ..... started
>> Local Products Rules ..... done
Creating test log file logs/slc7_amd64_gcc700/testing.log
Package FWCore/SharedMemory: Running test testFWCoreSharedMemoryMonitorThread

===== Test "testFWCoreSharedMemoryMonitorThread" ====

---> test testFWCoreSharedMemoryMonitorThread succeeded

^^^^ End Test testFWCoreSharedMemoryMonitorThread ^^^^
Package FWCore/SharedMemory: Running test testFWCoreSharedMemoryMonitorThreadSignals

===== Test "testFWCoreSharedMemoryMonitorThreadSignals" ====
/build/muz/x/CMSSW_10_6_X_2024-04-07-0000/src/FWCore/SharedMemory/test/test_monitor_thread_signals.sh: line 10: 2973439 Aborted                 (core dumped) ${CMSSW_BASE}/test/${SCRAM_ARCH}/testFWCoreSharedMemoryMonitorThread 6 &>testFWCoreSharedMemoryMonitorThread.log
/build/muz/x/CMSSW_10_6_X_2024-04-07-0000/src/FWCore/SharedMemory/test/test_monitor_thread_signals.sh: line 22: 2973448 Segmentation fault      (core dumped) ${CMSSW_BASE}/test/${SCRAM_ARCH}/testFWCoreSharedMemoryMonitorThread 11 &>testFWCoreSharedMemoryMonitorThread.log

---> test testFWCoreSharedMemoryMonitorThreadSignals succeeded

^^^^ End Test testFWCoreSharedMemoryMonitorThreadSignals ^^^^

[antoniovilela]

yMonitor

Many thanks Shahzad!

I wil abort this build and restart later.

[antoniovilela]

abort

[cmsbuild]

Deleting CMSSW_10_6_41:

• Release successfully deleted

• cmssw tag CMSSW_10_6_41 successfully deleted.

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

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