Hello *,
this is just an informal poll to check status at other sites;
we are having env. modules provided via a Debian package;
(environment-modules_3.2.10-1_amd64.deb) and get this kind of error:
```
sw@h-cluster1-1:~$ module whatis ROOT
ROOT/v5.34.01-ictce-4.0.6(18):ERROR:102: Tcl command execution failed: if {
![is-loaded ictce/4.0.6] } {
module load ictce/4.0.6
}
ROOT : The ROOT system provides a set of OO frameworks with all
the functionality
needed to handle and analyze large amounts of data in a very efficient way. -
Homepage: http://root.cern.ch/drupal/
```
Does it relate to the 64bit build of env. modules? Are we alone in this?
I suspect, but have no proof yet, that we hit a bug of this type:
http://sourceforge.net/mailarchive/message.php?msg_id=26547928
...since the error persists even if I feed modulefiles that are known to behave!
ps.
We released on Friday our most popular cluster back in production,
after a maintenance window, delivering >500 modules in production,
all thanks to v1.2.0; that was very good job everybody!!! Solid stuff.
We already get complaints that we have too many modules, people cannot
find them etc; unfortunately, it's true :) so, what are your workarounds?
The prospect of arriving the watermark of 1000 modules is within reach now
(in fact, we could just arrive there by just tool-chaining latest gcc/icc!)
so this is becoming a very very serious challenge. Should we split the
modulespace by toolchain? does that make sense in your eyes?
We may need to provide a wrapper command over here (module-find or such),
otherwise it's tough to navigate the plethora of provided builds.
I wonder what you guys do, any ideas welcome!
tia,
Fotis
ps. LRZ has an interesting idea of "module -d" for default versions only!
