Describe the Problem

Users/developers have experienced an error that only occurs occasionally. Rerunning the same command often resolves the issue. Here is an example:

CALLING: /home/mccabe/MET/internal/test_unit/python/unit.py /home/mccabe/MET/internal/test_unit/xml/unit_tc_stat.xml

TEST: tc_stat_ALAL2010

• FAIL - 0.688 sec

/home/mccabe/.conda/envs/my_test_env/share/met/../../bin/tc_stat
-lookin /d1/personal/mccabe/met_test_output/tc_pairs/alal2010.tcst
-config /home/mccabe/MET/internal/test_unit/config/TCStatConfig_ALAL2010
-out /d1/personal/mccabe/met_test_output/tc_stat/ALAL2010_stat.out
-v 2
ERROR :
ERROR : yyerror() -> syntax error in file "config_string"
ERROR :
ERROR : line = 2
ERROR :
ERROR : column = 0
ERROR :
ERROR : text = "(nul)"
ERROR :
ERROR :
ERROR : (nul)
ERROR : (nul)
ERROR :

ERROR: /home/mccabe/MET/internal/test_unit/python/unit.py unit_tc_stat.xml failed.

Expected Behavior

This error should not ever occur.

Environment

Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop)
2. OS: (e.g. RedHat Linux, MacOS)
3. Software version number(s)

To Reproduce

Describe the steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2702701 (NCAR base)

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as the next bugfix version
• Select Coordinated METplus-X.Y Support project for support of the current coordinated release
• Select MET-X.Y.Z Development project for development toward the next official release

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of main_<Version>.
  Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• Fix the bug and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into main_<Version>.
  Pull request: bugfix <Issue Number> main_<Version> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the next bugfix version
  Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Complete the steps above to fix the bug on the develop branch.
  Branch name: bugfix_<Issue Number>_develop_<Description>
  Pull request: bugfix <Issue Number> develop <Description>
  Select: Reviewer(s) and Development issue
  Select: Milestone as the next official version
  Select: MET-X.Y.Z Development project for development toward the next official release
• Close this issue.