don't raise error when required extensions are not found when installing extensions in parallel #4671
+22
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Raising an error effectively makes it impossible to use
--parallel-extensions-install
on bundle easyconfigs likeR-bundle-CRAN-2024.06-foss-2023b.eb
andR-bundle-Bioconductor-3.18-foss-2023a-R-4.3.2.eb
.There's actually no reason to give up when extensions that are required dependencies for an extension that will be installed are not included in
exts_list
, since they're probably provided via a dependency likeR
orR-bundle-CRAN
.Note that this is exactly what we do currently when installing extensions sequentially...
If a dependency of a particular extension is totally missing, the installation of that extension will fail as it does when installing sequentially.
Note: for using
--parallel-extensions-install
onR-bundle-CRAN
(or olderR
easyconfigs that includeRmpi
andRserve
), an additional bug fix is required, see:return
for customisedinstall_extension_async
methods in Rserve and Rmpi easyblocks easybuild-easyblocks#3474