Skip to content

Conversation

@Flamefire
Copy link
Contributor

@Flamefire Flamefire commented Dec 9, 2025

(created using eb --new-pr)

This adds a 2nd line to the existing error:

ERROR: One or more non-existing paths specified: NCCL-2.27.5-GCCcore-13.3.0-CUDA-12.6.0.eb, cuDNN-9.10.2.21-CUDA-12.6.0.eb, cuSPARSELt-0.6.3.2-CUDA-12.6.0.eb, Triton-3.5.0-gfbf-2024a-CUDA-12.6.0.eb, pyzstd-0.16.2-GCCcore-13.3.0.eb
Did you mean:  /git/easybuild-easyconfigs/easybuild/easyconfigs/t/Triton/Triton-3.5.0-gfbf-2024a-CUDA-12.6.0.eb,  /git/easybuild-easyconfigs/easybuild/easyconfigs/c/cuSPARSELt/cuSPARSELt-0.6.3.2-CUDA-12.6.0.eb,  /git/easybuild-easyconfigs/easybuild/easyconfigs/n/NCCL/NCCL-2.27.5-GCCcore-13.3.0-CUDA-12.6.0.eb,  /git/easybuild-easyconfigs/easybuild/easyconfigs/p/pyzstd/pyzstd-0.16.2-GCCcore-13.3.0.eb,  /git/easybuild-easyconfigs/easybuild/easyconfigs/c/cuDNN/cuDNN-9.10.2.21-CUDA-12.6.0.eb

However I don't like having to specify the full paths to easyconfigs in my dev tree/search-path when EB can and does already resolve them.

Shall we enhance it like:
If easyconfig is found and not ambiguous (could that even happen? Can't see how) then use its path (instead of showing its location)

@boegel boegel added this to the release after 5.2.0 milestone Dec 9, 2025
@Flamefire Flamefire force-pushed the 20251209133245_new_pr_vAOwMXfSHr branch from 7da7b2b to f00adea Compare December 10, 2025 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants