Closed zzhang147 closed 2 years ago
@zzhang147 More information is expected to understand what the issue is. Especially, could you provide the output of the following command:
$ module config -DD --dump-state
And also the content of all the RC files that will be mentioned by this debug report.
after a few minutes this issue not seen again.
After some searches, I have found that this error is obtained when the current working directory where the module command is executed is removed:
$ mkdir test
$ cd test
$ rmdir ../test
$ module
ERROR: error getting working directory name: no such file or directory
while executing
"pwd"
(procedure "getAbsolutePath" line 9)
invoked from within
"getAbsolutePath $fpath"
(procedure "cmdModuleSource" line 3)
invoked from within
"cmdModuleSource load $rc"
(procedure "runModulerc" line 23)
invoked from within
"runModulerc"
(procedure "module" line 110)
invoked from within
"{*}$execcmdlist"
Please report this issue at https://github.com/cea-hpc/modules/issues
I am updating code to make it clear this situation is not a modulecmd.tcl
issue.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Location and content of any modulerc or modulefile involved:
Expected behavior
Error and debugging information
Modules version and configuration
Additional context