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

Update the new merges #5

Merged
merged 2 commits into from
Feb 15, 2023
Merged

Update the new merges #5

merged 2 commits into from
Feb 15, 2023

Conversation

panll
Copy link
Owner

@panll panll commented Feb 15, 2023

--- Delete this line and those above before hitting "Create pull request" ---

DESCRIPTION OF CHANGES:

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

TESTS CONDUCTED:

  • hera.intel
  • orion.intel
  • cheyenne.intel
  • cheyenne.gnu
  • gaea.intel
  • jet.intel
  • wcoss2.intel
  • NOAA Cloud (indicate which platform)
  • Jenkins
  • fundamental test suite
  • comprehensive tests (specify which if a subset was used)

DEPENDENCIES:

DOCUMENTATION:

ISSUE:

CHECKLIST

  • My code follows the style guidelines in the Contributor's Guide
  • I have performed a self-review of my own code using the Code Reviewer's Guide
  • I have commented my code, particularly in hard-to-understand areas
  • My changes need updates to the documentation. I have made corresponding changes to the documentation
  • My changes do not require updates to the documentation (explain).
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • Any dependent changes have been merged and published

LABELS (optional):

A Code Manager needs to add the following labels to this PR:

  • Work In Progress
  • bug
  • enhancement
  • documentation
  • release
  • high priority
  • run_ci
  • run_we2e_fundamental_tests
  • run_we2e_comprehensive_tests
  • Needs Cheyenne test
  • Needs Jet test
  • Needs Hera test
  • Needs Orion test
  • help wanted

CONTRIBUTORS (optional):

mkavulich and others added 2 commits February 14, 2023 09:55
…provements (#600)

This is another round of improvements for the pythonized WE2E test scripts. I was originally going to wait until the script was ready to replace, but I accidentally forgot to make a change to a final log message in monitor_jobs.py; this results in a scary-looking error message even though all experiments may have completed successfully.

The solution was simply to replace the undefined variable with a correct one.

This PR comes from an in-progress branch for improvements to the python scripts, so a few other improvements are coming along with this bug fix:

* When monitor_jobs.py is called for the first time, it will check the status of all jobs, not just those that are incomplete. 
 This will allow users to use this script to monitor a previously failed job that has been fixed.
* Add checks for proper run_envir, and add all needed variables for run_envir=nco mode.
* Fix another incorrect error message in setup.py.
Currently if you grep for unbound variables in your experiement directories log files, you will find many BASH_SOURCE: unbound variables messages, which may cause confusion when one is debugging a problem. The culprit files are filesys_cmds_vrfy.sh, print_msg.sh, change_cases.sh and preamble.sh. This PR fixes these files, so there should not be any unbound variables in the log files now.  Additionally, updated .cicd/Jenkinsfile to keep tests from running on Hera (which is currently down in the Jenkins CI pipeline.

---------

Co-authored-by: Michael Lueken <[email protected]>
@panll panll merged commit 107c001 into panll:develop Feb 15, 2023
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.

3 participants