-
Notifications
You must be signed in to change notification settings - Fork 214
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
Get some unit testing defaults from config_machines #872
Comments
It looks like mpilib and compiler can pick up defaults now, although some tweaks are needed:
Ideally, the mpirun command would still be picked up by default. In addition, it would be nice if |
Unit testing: Determine machine-specific settings automatically This PR allows you to run the unit tests by simply running tools/unit_testing/run_tests.py without any additional arguments. The machine, compiler, mpilib, and mpirun command are now determined automatically. In addition, use-openmp is now assumed by default, since that is the standard way we build pFUnit (but there is a mechanism to turn off use-openmp). This is important in order to support unit testing on additional machines. In order to accomplish this, I needed to tweak some pieces that are also used by system builds: (1) I added a unit_testing attribute to the mpirun command in config_machines.xml. This is needed on yellowstone, where we use a complex command to launch CESM, but just want to use a simple 'mpirun.lsf' to launch unit tests. (2) In machines.py: probe_machine_name: If no name is found with socket.getfqdn(), then try socket.gethostname(). This is needed in order to determine the machine when running on my laptop. Test suite: scripts_regression_tests on yellowstone Also ran unit tests on yellowstone using the trimmed-down command documented in README.unit_testing. And ran unit tests on my laptop using the same command. Test baseline: N/A Test namelist changes: none Test status: bit for bit Fixes #872 User interface changes?: Simplifies the typical call to run_tests.py Code review: jedwards
From @billsacks on August 4, 2015 17:6
With the changes here:
CESM-Development#87
a number of machine-specific settings need to be explicitly specified when running run_tests.py; these should be obtained from config_machines:
@quantheory suggested this; he and @jedwards4b seem like the ones who would know how to do this.
Copied from original issue: CESM-Development#92
The text was updated successfully, but these errors were encountered: