Taking the following modulefiles as example:
$ module show da db df
-------------------------------------------------------------------
/path/to/modulefiles/da:
conflict df
-------------------------------------------------------------------
/path/to/modulefiles/db:
-------------------------------------------------------------------
/path/to/modulefiles/df:
prereq da db
-------------------------------------------------------------------
When loading df with automated module handling mode enabled, it will first attempt to load da requirement and then will try to load db if da fails to load. da fails to load as it declares a conflict toward df so db is loaded as df requirement.
$ module load --auto df
Loading da
ERROR: da cannot be loaded due to a conflict.
HINT: Conflict with df is set in da.
Loading df
Loading requirement: db
$ module list
Currently Loaded Modulefiles:
1) db 2) df
What is confusing is that the load tentative of da and its error message is displayed even if db is loaded afterward and as a result df load succeed. da load message should be hidden to avoid confusion.
Taking the following modulefiles as example:
When loading
dfwith automated module handling mode enabled, it will first attempt to loaddarequirement and then will try to loaddbifdafails to load.dafails to load as it declares a conflict towarddfsodbis loaded asdfrequirement.What is confusing is that the load tentative of
daand its error message is displayed even ifdbis loaded afterward and as a resultdfload succeed.daload message should be hidden to avoid confusion.