-
Notifications
You must be signed in to change notification settings - Fork 117
use --force when purging all loaded modules with Lmod, to ensure sticky modules also get unloaded #307
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
Conversation
…ky modules also get unloaded
|
Can I test this patch? |
|
Good catch, @boegel! We don't run Lmod in production, so our testing uses mostly the basic setup. Thanks for submitting the fix. |
|
@jenkins-cscs retry all |
|
@vkarak Can you clarify what |
|
@boegel Indeed, the purpose of |
vkarak
left a comment
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.
@boegel I've done a PR into your branch adding a small comment for your fix.
Sorry for the delay in approving your PR, but I was quite busy last week and I wanted also to check whether it made sense to extend our internal API with a force option, but eventually, I don't think there is such need, cos we are not using unload_all in any case.
Add note about force purge in Lmod backend
Codecov Report
@@ Coverage Diff @@
## master #307 +/- ##
==========================================
+ Coverage 91.46% 91.46% +<.01%
==========================================
Files 66 66
Lines 7805 7807 +2
==========================================
+ Hits 7139 7141 +2
Misses 666 666
Continue to review full report at Codecov.
|
When running
./test_reframe.py -v, one test was failing on our system:This occurs because we are using Lmod and we have one "sticky" module (cfr.https://lmod.readthedocs.io/en/latest/240_sticky_modules.html) loaded, which only gets unloaded with
module --force purge, see below.I'm not sure whether this is the correct fix though, it depends for what purpose
unload_allis actually being used... The stickyclustermodule we have sets up$MODULEPATHfor example, so if it's unloaded the modules we provide centrally will no longer be available...Another way to fix this would be to check differently in the test whether
unload_allunloads the previously loaded modules...