{lib}[gfbf/2024a] nvidia-cutlass v3.8.0.0 w/ CUDA 12.6.0

[Flamefire]

(created using eb --new-pr)

Requires:

• {lib}[gfbf/2024a] CUDA-Python v12.6.2.post1 w/ CUDA 12.6.0 #23588
• Take into account alternative name post_install_patches when checking checksums easybuild-framework#5017

Benefits from:

• Honor sanity_check_commands & sanity_check_paths from extensions easybuild-framework#5012

[Flamefire]

Test report by @Flamefire
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in total)
c144 - Linux AlmaLinux 9.4, x86_64, AMD EPYC 9334 32-Core Processor (zen4), 4 x NVIDIA NVIDIA H100, 560.35.03, Python 3.9.18
See https://gist.github.com/Flamefire/c4914db7b36376532ebd0bad008996f0 for a full test report.

[Flamefire]

Test report by @Flamefire
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in total)
login1.alpha.hpc.tu-dresden.de - Linux Rocky Linux 9.6, x86_64, AMD EPYC 7352 24-Core Processor (zen2), Python 3.9.21
See https://gist.github.com/Flamefire/e7562f53c0ea9b272a4174f4dbf45b08 for a full test report.

[smoors]

@boegelbot please test @ jsc-zen3-a100

[boegelbot]

@smoors: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de

PR test command 'if [[ develop != 'develop' ]]; then EB_BRANCH=develop ./easybuild_develop.sh 2> /dev/null 1>&2; EB_PREFIX=/home/boegelbot/easybuild/develop source init_env_easybuild_develop.sh; fi; EB_PR=23606 EB_ARGS= EB_CONTAINER= EB_REPO=easybuild-easyconfigs EB_BRANCH=develop /opt/software/slurm/bin/sbatch --job-name test_PR_23606 --ntasks=8 --partition=jsczen3g --gres=gpu:1 ~/boegelbot/eb_from_pr_upload_jsc-zen3.sh' executed!

• exit code: 0
• output:

Submitted batch job 8236

Test results coming soon (I hope)...

Details

- notification for comment with ID 3384551966 processed

Message to humans: this is just bookkeeping information for me,
it is of no use to you (unless you think I have a bug, which I don't).

[boegelbot]

Test report by @boegelbot
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in total)
jsczen3g1.int.jsc-zen3.fz-juelich.de - Linux Rocky Linux 9.6, x86_64, AMD EPYC-Milan Processor (zen3), 1 x NVIDIA NVIDIA A100 80GB PCIe, 580.82.07, Python 3.9.21
See https://gist.github.com/boegelbot/18813d6b5191069ac8b3c30a75b15fc0 for a full test report.

[Flamefire]

If you can take a look at easybuilders/easybuild-framework#5012 please as the feature/fix is used here. I.e. without that this part of the sanity check is skipped

[Flamefire]

Test report by @Flamefire
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in total)
c144 - Linux AlmaLinux 9.4, x86_64, AMD EPYC 9334 32-Core Processor (zen4), 4 x NVIDIA NVIDIA H100, 560.35.03, Python 3.9.18
See https://gist.github.com/Flamefire/a678e814af4a8ef9e743e484018410d0 for a full test report.

[Thyre]

Test report by @Thyre
SUCCESS
Build succeeded for 4 out of 4 (1 easyconfigs in total)
ZAM054 - Linux Zorin OS 17, x86_64, 12th Gen Intel(R) Core(TM) i7-1260P, 1 x NVIDIA NVIDIA GeForce MX550, 580.65.06, Python 3.10.12
See https://gist.github.com/Thyre/f6215b7ae903ef425145633c324c2bf7 for a full test report.

[Thyre]

We should absolutely take a look at the framework PR.
I don't think this EasyConfig should be held back by it though.

[pavelToman]

Test report by @pavelToman
SUCCESS
Build succeeded for 3 out of 3 (1 easyconfigs in total)
node4307.litleo.os - Linux RHEL 9.6, x86_64, AMD EPYC 9454P 48-Core Processor, 1 x NVIDIA NVIDIA H100 NVL, 580.95.05, Python 3.9.21
See https://gist.github.com/pavelToman/98cbcd746d46394aaa1e112939255442 for a full test report.

[pavelToman]

Test report by @pavelToman
SUCCESS
Build succeeded for 3 out of 3 (1 easyconfigs in total)
node3903.accelgor.os - Linux RHEL 9.6, x86_64, AMD EPYC 7413 24-Core Processor, 1 x NVIDIA NVIDIA A100-SXM4-80GB, 580.95.05, Python 3.9.21
See https://gist.github.com/pavelToman/98bcd55a20699491ef6cbbed9ceed075 for a full test report.

[boegel]

I tested this on top of easybuilders/easybuild-framework#5012, to verify that the feature works, but that PR needs some love before it can get merged.

It's not strictly blocking this easyconfig PR though, because the extension-specific sanity checks are a nice to have.

I'm not even sure they really should be extension-specific, we could just move those checks to the top-level sanity_check_commands, and there wouldn't be a significant downside?

[Flamefire]

I'm not even sure they really should be extension-specific, we could just move those checks to the top-level sanity_check_commands, and there wouldn't be a significant downside?

sanity_check_commands might be fine, but sanity_check_paths overwrites the (useful) defaults and hence leads to mistakes if we put sanity_check_commands at the top level looking like the other could also be there.

Additionally to me it makes sense to keep stuff local: If we had 2 extensions then it would be strange to have the additional sanity check commands only for one.

[boegel]

I'm not even sure they really should be extension-specific, we could just move those checks to the top-level sanity_check_commands, and there wouldn't be a significant downside?

sanity_check_commands might be fine, but sanity_check_paths overwrites the (useful) defaults and hence leads to mistakes if we put sanity_check_commands at the top level looking like the other could also be there.

Additionally to me it makes sense to keep stuff local: If we had 2 extensions then it would be strange to have the additional sanity check commands only for one.

The sanity check is run after installing extensions, so you can list the commands for all extensions through top-level sanity_check_commands.

W.r.t. sanity_check_paths: you can combine top-level sanity_check_paths with enhance_sanity_check = True, and then the defaults won't be overridden.

[Flamefire]

The sanity check is run after installing extensions, so you can list the commands for all extensions through top-level sanity_check_commands.

I meant that e.g. only 1 extension requires a custom command and if having multiple extensions it might not be immediately clear a) to which extension this applies and b) why only for this one.
To me it is clearer if that is localized.
If you prefer I can update this to use the top-level checks.

W.r.t. sanity_check_paths: you can combine top-level sanity_check_paths with enhance_sanity_check = True, and then the defaults won't be overridden.

I forgot about that option and that we had it fixed a while ago, so yes that is an option now

[boegel]

The sanity check is run after installing extensions, so you can list the commands for all extensions through top-level sanity_check_commands.

I meant that e.g. only 1 extension requires a custom command and if having multiple extensions it might not be immediately clear a) to which extension this applies and b) why only for this one. To me it is clearer if that is localized. If you prefer I can update this to use the top-level checks.

I think for now it would make sense to use top-level stuff in this easyconfig.

We can still localize stuff later if/when easybuilders/easybuild-framework#5012 gets merged.

[boegel]

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (total: 1 min 0 secs) (1 easyconfigs in total)
node3903.accelgor.os - Linux RHEL 9.6, x86_64, AMD EPYC 7413 24-Core Processor (zen3), 1 x NVIDIA NVIDIA A100-SXM4-80GB, 580.95.05, Python 3.9.21
See https://gist.github.com/boegel/8347e134d01d07224f30b7760a41a5b8 for a full test report.

[boegel]

@boegelbot please test @ jsc-zen3-a100

[boegelbot]

@boegel: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de

PR test command 'if [[ develop != 'develop' ]]; then EB_BRANCH=develop ./easybuild_develop.sh 2> /dev/null 1>&2; EB_PREFIX=/home/boegelbot/easybuild/develop source init_env_easybuild_develop.sh; fi; EB_PR=23606 EB_ARGS= EB_CONTAINER= EB_REPO=easybuild-easyconfigs EB_BRANCH=develop /opt/software/slurm/bin/sbatch --job-name test_PR_23606 --ntasks=8 --partition=jsczen3g --gres=gpu:1 ~/boegelbot/eb_from_pr_upload_jsc-zen3.sh' executed!

• exit code: 0
• output:

Submitted batch job 9256

Test results coming soon (I hope)...

Details

- notification for comment with ID 3674539639 processed

Message to humans: this is just bookkeeping information for me,
it is of no use to you (unless you think I have a bug, which I don't).

[boegelbot]

Test report by @boegelbot
SUCCESS
Build succeeded for 1 out of 1 (total: 1 min 50 secs) (1 easyconfigs in total)
jsczen3g1.int.jsc-zen3.fz-juelich.de - Linux Rocky Linux 9.6, x86_64, AMD EPYC-Milan Processor (zen3), 1 x NVIDIA NVIDIA A100 80GB PCIe, 580.95.05, Python 3.9.21
See https://gist.github.com/boegelbot/9560312e94cfd6addc3bf7d7504ef300 for a full test report.

[boegel]

Going in, thanks @Flamefire!