You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ module show mb mc me mf
-------------------------------------------------------------------
/path/to/modulefiles/mb:
module load mc
-------------------------------------------------------------------
/path/to/modulefiles/mc:
module unload mc
-------------------------------------------------------------------
/path/to/modulefiles/me:
module load mb
module load mf
-------------------------------------------------------------------
/path/to/modulefiles/mf:
module unload mc
-------------------------------------------------------------------
When loading me, its requirements express conflicting needs. mc is first loaded by mb then mf attempts to remove it. However failing automated unload of mc is not reported and a confusing message suggesting the unload should be done is returned:
$ module load me
Unloading mc
ERROR: mc cannot be unloaded due to a prereq.
HINT: Might try "module unload mb" first.
Loading mf
ERROR: mf cannot be loaded due to a conflict.
HINT: Might try "module unload mc" first.
Loading me
ERROR: me cannot be loaded due to missing prereq.
HINT: the following module must be loaded first: mf
The text was updated successfully, but these errors were encountered:
When loading a module, report any loaded conflict on the message
reporting block corresponding to this module load. This warning or error
message comes in addition to the eventual conflict unload message
reported under the message block of the main evaluation.
When a module load is forced and a conflict of this module is loaded,
report this conflict with the same concise message (no hint) whether an
unload of this conflicting module was attempted or not.
Fixes#261.
Taking following modules as example:
When loading
me
, its requirements express conflicting needs.mc
is first loaded bymb
thenmf
attempts to remove it. However failing automated unload ofmc
is not reported and a confusing message suggesting the unload should be done is returned:The text was updated successfully, but these errors were encountered: