Skip to content
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

Test CI: Pull Requests #188

Closed

Conversation

manishvenu
Copy link
Collaborator

@manishvenu manishvenu commented Aug 29, 2024

Test CI on ESCOMP:138-set-up-github-actions-ci-testing

@manishvenu manishvenu closed this Aug 29, 2024
@manishvenu manishvenu deleted the MOO branch August 29, 2024 22:53
alperaltuntas pushed a commit that referenced this pull request Sep 4, 2024
This PR fixes Issue #138, which was about implementing CI in MOM_Interface with four initial tasks. Please reference back to the issue for those requirements.

Changes Introduced by this PR:

A GitHub Action Workflow (please see below for details) under .github/workflows/general-ci-tests.yml
Incidentally, Black formatting on two scripts in cime_config
CI/Github Action Workflow Details:

Workflow is structured into three independent jobs that are triggered on push and pull-request events onto the main branch:

checking the black format of scripts in cime_config
running the check_default_params test under the tests folder
building the standalone MOM6 and running two lightweight MOM6 examples (double_gyre, single_column/KPP)
Testing:

Test Failures: The bottom two jobs (2 & 3) were tested by creating an error (See Commits starting with Test CI), and the first job with Black formatting was already failing (commit) and was corrected early on in the process.
Test Events/Triggers: Every job in the commit history was triggered on a push. Pull-Requests were tested in Test CI: Pull Requests #188.
Notes:

The commits should (need?) be squashed. (My fault, hah)
Checking out the correct MOM branch for the standalone build is a little trickier because we are starting with the CESM repo. To be safe, the triggering event is manually checked out instead of using the common Github action actions/checkout@v4 (See the steps Checkout initial event (Pull Request) and Checkout initial event (Push)).
I think the workflow is pretty easy to read through, but would welcome any advice/help on the clarity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant