2.0 - Dynamic Module Loads #51
Description
One of the core problems test run into is the difference between environments, and especially the module environments, on various systems. In pavilion 2.0, both build scripts and run scripts can include a list of modules to load before commands are executed (See the related tickets below). The problem of how to load this modules remains. To fix this issue, there will be a plugin system for describing how to load modules.
By default, for every module specified, a simple 'module load <module_name/version>' line will be added to test build and test run scripts.
Module Handler Plugins
To override the defaults, a plugin will need to be created. The plugin base class will operate as follows.
Host List
The plugin class will include a list of hosts to which it applies. These will be checked on activation to eliminate plugin conflicts.
Module loaders
The class will include a dict of module loaders; functions that take the (os, host, network, module_version) and produce a list of commands to run to load that module and a list of environment variables to set. For example, for the cle6 module handler, we might include a loader for gcc that module swaps PrgEnv-intel for PrgEnv-gnu of the relevant version, and sets CC=cc. Thus, builds/test runs that ask for gcc on cray would end up with the right environment and the cray compiler wrapper.