Repository navigation
Conversation
added 2 commits
October 21, 2026 12:19
…ive builds, as they were introduced in EESSI/software-layer-scripts#321
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
EESSI/software-layer-scripts#321 introduces the ability to debug our builds interactively, in a way that is virtually identical to how the bot does it. Essentially, this is done by running:
in the job directory left behind by the build bot.
One issue with that approach is that
bot-build.slurmcallsbot/build.shfromsoftware-layer. This tries to (re)clonesoftware-layer-scripts, which fails (and exits, because ofset -e) when this is done in an existing staged job directory left behind by the build bot.This PR solves that by making bot/build.sh skip cloning of software-layer-scripts for interactive builds (i.e. if EESSI_INTERACTIVE_BUILD is non-empty).