Github workflow to run unit tests without CIME

[glemieux]

Description:

This pull request creates a workflow to automate the running of run_unit_tests with new pull requests. This will attempt to address the issues with breaking unit tests during the course of nominal FATES development (which #1423 addressed).

The design of this workflow is to run the testing in a container that has the necessary dependencies and CIME infrastructure to handle the unit test dummy case build. The container build workflow and dockerfiles are held in a separate repository (https://github.com/NGEET/containers).

Collaborators:

Expectation of Answer Changes:

Checklist

If this is your first time contributing, please read the CONTRIBUTING document.

All checklist items must be checked to enable merging this pull request:

Contributor

• The in-code documentation has been updated with descriptive comments
• The documentation has been assessed to determine if updates are necessary

Integrator

• FATES PASS/FAIL regression tests were run
• Evaluation of test results for answer changes was performed and results provided

Documentation

• Technical Note update:
• User's Guide update:

Test Results:

CTSM (or) E3SM (specify which) test hash-tag:

CTSM (or) E3SM (specify which) baseline hash-tag:

FATES baseline hash-tag:

Test Output:

[glemieux]

This build is currently failing with the following error:

ERROR: Could not initialize machine object from //ccs_config/machines/config_machines.xml, /root/.cime/config_machines.xml. This machine is not available for the target CIME_MODEL.
Error: Process completed with exit code 1.

So it appears to be finding the config file in the container's .cime directory and the hostname/machine name should match the custom config, so I'm not sure why is says it can find the target for CIME_MODEL=cesm. I'm wondering if there is something that CIME is assuming for a cesm file structure that isn't present in this CIME-only container.