-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restore initial environment before processing each easystack item #4213
restore initial environment before processing each easystack item #4213
Conversation
Tests are failing because of:
But I have no clue what's causing this, doesn't seem related to this PR? |
@bedroge That test is failing because in it we assume that the build environment does not get reset after the installation of easyconfigs, which the change you propose (which does make sense) is breaking... |
…asystack (rather than restoring environment after installing a series of easyconfigs in build_and_install_software)
@bedroge The failing test is actually telling us that we're making a somewhat intrusive change. Here's a proposal for a different approach: bedroge#1 |
restore environment before processing an easystack entry in process_easystack
Looks good, merged! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Closes #4194 by explicitly restoring the environment at the end of
build_and_install_software
. This should prevent that the dependencies of a previous (set of) installation(s) are still loaded for the next one, e.g. when using an easystack file. Also added a test that verifies this.Test output before applying the patch to
main.py
:After applying the patch: