You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary of Issue: The RE_TRACKING reg ex in repository_git.py appears to be too restrictive.
Expected behavior and actual behavior:I have a clm checkout that looks like
git status
On branch pio2_cleanup
Your branch and 'mydev/pio2_cleanup' have diverged,
and have 62 and 2 different commits each, respectively.
(use "git pull" to merge the remote branch into yours)
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: src/main/ncdio_pio.F90.in
no changes added to commit (use "git add" and/or "git commit -a")
…chey_pes
Update pes layout for f19_g17 B1850 on cheyenne
A better layout for the f19_g17 B1850 configuration on cheyenne for the tutorial.
Getting 12 simulated years per day.
Summary of Issue: The RE_TRACKING reg ex in repository_git.py appears to be too restrictive.
Expected behavior and actual behavior:I have a clm checkout that looks like
Current behavior is:
If I changes the RE_TRACKING to be RE_TRACKING = re.compile(r'[(.+)]')
then I get what I think that I should expect:
Steps to reproduce the problem. Include externals description file(s) and link to public repository):
What is the changeset ID of the code, and the machine you are using:
have you modified the code? If so, it must be committed and available for testing:
Screen output or log file showing the error message and context:
The text was updated successfully, but these errors were encountered: