run the check_missing_installations.sh
script with the EB version from the easystack filename
#1094
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.
By not specifying the version, it would always use the latest EB version. That could lead to annoying issues, for instance the issue observed in #1086: it started running the checks for some targets with EB 5.1.0 (which just got ingested), and in this version Java 21 was updated to point to Java 21.0.7 instead of 21.0.5. By always sticking to the EB version that's encoded in the easystack filename, this should not happen. We already do the same in
EESSI-installsoftware.sh
, see https://github.com/EESSI/software-layer/blob/2023.06-software.eessi.io/EESSI-install-software.sh#L362.