alpaka: use the HEAD of the develop branch

[fwyzard]

This PR is to be used to regularly test that the HEAD of the alpaka develop branch is compatible with CMSSW.

[cmsbuild]

cms-bot internal usage

[fwyzard]

please test

[cmsbuild]

-1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9cab57/46197/summary.html
COMMIT: e1b849c
CMSSW: CMSSW_15_1_X_2025-05-15-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmsdist/9872/46197/install.sh to create a dev area with all the needed externals and cmssw changes.

External Build

I found compilation warning when building: See details on the summary page.

[cmsbuild]

Pull request #9872 was updated.

[fwyzard]

please test

[fwyzard]

@smuzaffar @iarspider if these tests work, do you think we could run something like this more regularly ?
Something like, once a day, and only if any changes were pushed to alpaka ?

[cmsbuild]

Pull request #9872 was updated.

[fwyzard]

please test

[smuzaffar]

@smuzaffar @iarspider if these tests work, do you think we could run something like this more regularly ? Something like, once a day, and only if any changes were pushed to alpaka ?

@fwyzard , this should work and should use the latest commit of alpaka's selected branch. For now we can run manually once a day but we will soon hit the commit status limit.

[fwyzard]

If it's manual, I can trigger it when something gets merged in alpaka, and rebase it once in a while to update the commit.

[fwyzard]

More in general I was wondering if we could set up some automatic testing of the dependencies that we have, like also ROOT, to spot potential problems earlier.

[smuzaffar]

for root we have dedicated IBs and we manually update root commits once a week. so ROOT automatic testing it done via daily IBs. We can setup new ALPAKA IBs where alpaka get latest commit automatically and we build such IB few times a week

[fwyzard]

for root we have dedicated IBs and we manually update root commits once a week

Eh, so not very much automatic :)

[fwyzard]

Mhm, I would not add another set of IBs to test alpaka, doing PR-like tests should be enough for now.

I'm mostly interested in making sure that alpaka does not break the syntax we use.

[smuzaffar]

correct, we do want to run few IBs for every root update to catch any threading issue

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9cab57/46200/summary.html
COMMIT: 9a49f5f
CMSSW: CMSSW_15_1_X_2025-05-15-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmsdist/9872/46200/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

• @cms-sw rdma-core: Rename Patch to Patch0 #9871

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9cab57/46200/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9cab57/46200/git-merge-result

Comparison Summary

Summary:

• You potentially added 3 lines to the logs
• Reco comparison results: 6 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 4038193
• DQMHistoTests: Total failures: 3
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 4038170
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 215 log files, 184 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[fwyzard]

Note: the latest tests correspond to alpaka-group/alpaka@e906b1c .

[fwyzard]

please test

[cmsbuild]

-1

Failed Tests: UnitTests
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9cab57/46621/summary.html
COMMIT: 9a49f5f
CMSSW: CMSSW_15_1_X_2025-06-09-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmsdist/9872/46621/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found 7 errors in the following unit tests:

---> test alpakaTestAtomicPairCounterSerialSync had ERRORS
---> test alpakaTestHistoContainerSerialSync had ERRORS
---> test alpakaTestIndependentKernelSerialSync had ERRORS
and more ...

Comparison Summary

Summary:

• You potentially added 15 lines to the logs
• Reco comparison results: 8 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 4048495
• DQMHistoTests: Total failures: 6
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 4048469
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 215 log files, 184 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[fwyzard]

please test

[cmsbuild]

-1

Failed Tests: Build
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9cab57/46827/summary.html
COMMIT: 9a49f5f
CMSSW: CMSSW_15_1_X_2025-06-18-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmsdist/9872/46827/install.sh to create a dev area with all the needed externals and cmssw changes.

Build

I found compilation error when building:

>> Subsystem Utilities built
Copying tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaMoveToDeviceAsyncROCmAsync/libalpakaMoveToDeviceAsyncROCmAsync_rocm.a to productstore area:
Copying tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaTestAtomicPairCounterROCmAsync/libalpakaTestAtomicPairCounterROCmAsync_rocm.a to productstore area:
cp: cannot stat 'tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaMoveToDeviceAsyncROCmAsync/libalpakaMoveToDeviceAsyncROCmAsync_rocm.a': No such file or directory
>> Deleted: tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaMoveToDeviceAsyncROCmAsync/libalpakaMoveToDeviceAsyncROCmAsync_rocm.a
gmake: *** [config/SCRAM/GMake/Makefile.rules:1920: tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaMoveToDeviceAsyncROCmAsync/libalpakaMoveToDeviceAsyncROCmAsync_rocm.a] Error 1
cp: cannot stat 'tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaTestAtomicPairCounterROCmAsync/libalpakaTestAtomicPairCounterROCmAsync_rocm.a': No such file or directory
>> Deleted: tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaTestAtomicPairCounterROCmAsync/libalpakaTestAtomicPairCounterROCmAsync_rocm.a
gmake: *** [config/SCRAM/GMake/Makefile.rules:1920: tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaTestAtomicPairCounterROCmAsync/libalpakaTestAtomicPairCounterROCmAsync_rocm.a] Error 1
Copying tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaTestBufferROCmAsync/libalpakaTestBufferROCmAsync_rocm.a to productstore area:
cp: cannot stat 'tmp/el8_amd64_gcc12/src/HeterogeneousCore/AlpakaInterface/test/alpakaTestBufferROCmAsync/libalpakaTestBufferROCmAsync_rocm.a': No such file or directory