-
Notifications
You must be signed in to change notification settings - Fork 365
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1343 from billsacks/run_tests_defaults
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
- Loading branch information
Showing
8 changed files
with
87 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters