{2025.06}[2025a] Scalasca 2.6.2

[bedroge]

An older version for 2023.06 failed to build due to Qt6 issues (see #800), but we do already have Qt6 for 2025a, so let's try this one instead.

[bedroge]

bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2025.11/pr_1284/101563

date	job status	comment
Nov 04 09:56:17 UTC 2025	submitted	job id 101563 awaits release by job manager
Nov 04 09:56:29 UTC 2025	released	job awaits launch by Slurm scheduler
Nov 04 10:02:31 UTC 2025	running	job 101563 is running
Nov 04 10:53:33 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-101563.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2025.06-software-linux-x86_64-amd-zen2-17622535350.tar.gz size: 62 MiB (65829900 bytes) entries: 624 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all Scalasca/2.6.2-gompi-2025a.lua Score-P/9.0-gompi-2025a.lua software under 2025.06/software/linux/x86_64/amd/zen2/software Scalasca/2.6.2-gompi-2025a Score-P/9.0-gompi-2025a reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod Scalasca/2.6.2-gompi-2025a/20251104_105122UTC Score-P/9.0-gompi-2025a/20251104_104512UTC other under 2025.06/software/linux/x86_64/amd/zen2 no other files in tarball
Nov 04 10:53:33 UTC 2025	test result	😁 SUCCESS (click triangle for details) ReFrame Summary [ PASSED ] Ran 0/0 test case(s) from 0 check(s) (0 failure(s), 0 skipped, 0 aborted) Details ✅ job output file slurm-101563.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case

[eessi-bot-jsc]

New job on instance eessi-bot-jsc for repository eessi.io-2025.06-software
Building on: nvidia-grace
Building for: aarch64/nvidia/grace
Job dir: /p/project1/ceasybuilders/eessibot/jobs/2025.11/pr_1284/14179757

date	job status	comment
Nov 04 09:56:19 UTC 2025	submitted	job id 14179757 awaits release by job manager
Nov 04 09:57:13 UTC 2025	released	job awaits launch by Slurm scheduler
Nov 04 09:58:17 UTC 2025	running	job 14179757 is running
Nov 04 10:24:03 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-14179757.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2025.06-software-linux-aarch64-nvidia-grace-17622515710.tar.gz size: 61 MiB (64610251 bytes) entries: 624 modules under 2025.06/software/linux/aarch64/nvidia/grace/modules/all Scalasca/2.6.2-gompi-2025a.lua Score-P/9.0-gompi-2025a.lua software under 2025.06/software/linux/aarch64/nvidia/grace/software Scalasca/2.6.2-gompi-2025a Score-P/9.0-gompi-2025a reprod directories under 2025.06/software/linux/aarch64/nvidia/grace/reprod Scalasca/2.6.2-gompi-2025a/20251104_101750UTC Score-P/9.0-gompi-2025a/20251104_101612UTC other under 2025.06/software/linux/aarch64/nvidia/grace no other files in tarball
Nov 04 10:24:03 UTC 2025	test result	😁 SUCCESS (click triangle for details) ReFrame Summary [ PASSED ] Ran 0/0 test case(s) from 0 check(s) (0 failure(s), 0 skipped, 0 aborted) Details ✅ job output file slurm-14179757.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case

[Thyre]

I‘d propose to filter the Score-P dependency, since that prevents a bit of headache when dealing with the different Score-P versions present in 2025a.

Scalasca calls scorep as a command, but doesn‘t link to any shared library or include any headers.

I‘ll probably do this for 2025b, but haven‘t done it for 2025a…

---

Alternatively, we can include both Score-P & CubeGUI here, but bump Score-P to v9.3 (probably in a hook?). That will also work out fine. It's unlikely that we'll add newer versions of Score-P, Scalasca and CubeGUI to 2025a, as Score-P and Scalasca depend on CubeLib where a new release is imminent. So they'd go into 2025b.