Skip to content
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

Module with reflexive conflict fails to load by its full pathname #352

Closed
xdelaruelle opened this issue Jul 29, 2020 · 1 comment
Closed
Labels
Milestone

Comments

@xdelaruelle
Copy link
Member

When a modulefile defines a reflexive conflict (to ensure only one version of the module is loaded):

$ module -V
Modules Release 4.5.1 (2020-06-01)
$ module use /path/to/modfiles
$ module avail
---------------- /path/to/modfiles -----------------
mod/1  
$ cat /path/to/modfiles/mod/1
#%Module
conflict mod

An error is obtained when this module is loaded by its full pathname:

$ module load /path/to/modfiles/mod/1
Loading /path/to/modfiles/mod/1
  ERROR: /path/to/modfiles/mod/1 cannot be loaded due to a conflict.
    HINT: Might try "module unload mod" first.
@xdelaruelle xdelaruelle added this to the 4.5.2 milestone Jul 29, 2020
@xdelaruelle
Copy link
Member Author

This issue was first reported on RH bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1860674

xdelaruelle added a commit to xdelaruelle/modules that referenced this issue Jul 29, 2020
Adapt conflict detection tests to ensure a module loaded by its full
pathname will not detect itself as a conflict when declaring a reflexive
conflict.

Fixes cea-hpc#352.
xdelaruelle added a commit to xdelaruelle/modules that referenced this issue Jul 30, 2020
Adapt conflict detection tests to ensure a module loaded by its full
pathname will not detect itself as a conflict when declaring a reflexive
conflict.

Fixes cea-hpc#352.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant