Closed guusbertens closed 8 months ago
Thanks very much for the bug report! As you noticed this bug occurred when command line name was "break/break" and not "break". Lmod keeps track of the requested modules to be loaded. Lmod missed the case where where the userName ("break/break") and the shortName, (sn: "break") were different. This is now fixed for me with Lmod 8.7.37.
Please test the latest version of Lmod to see if it works for you. If it does then feel free to close this issue.
Robert, thanks, this indeed fixes the issue!
Describe the bug
LmodBreak errors when loading an explicit module. When loading a directory, i.e.
module load dir
, it behaves as expected, but when loading a module from that directory, i.e.module load dir/module
, Lmod errors out and no other modules get loaded.To Reproduce
Lmod output for the last command:
Expected behavior
Based on the documentation ("However, all other modulefiles are evaluated."), I expect Lmod to continue loading
other
in either case.Desktop (please complete the following information):
miniConfig for Lmod 8.7.36: