-
Notifications
You must be signed in to change notification settings - Fork 15
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
zppy errors in E3SM Unified 1.9.2rc2 #538
Comments
Thanks for the clear description. I've crossed out the commits that I know wouldn't affect e3sm_diags between v2.9.0 and v2.10.0. Can you provide me the standalone command for the e3sm_diags task? I will try stepping through the code on v2.10.0 up to where it breaks. |
Hmm I'm trying to figure out exactly how to condense that down. There's a lot of auto-generation (and NCO dependencies) that come first. The relevant parts of the Excerpt of tests/integration/generated/test_bundles_chrysalis.cfg
So, that ends up generating a e3sm_diags_atm_monthly_180x360_aave_environment_commands_model_vs_obs_1850-1851.bash
So, the command is really |
Ah, ok, I think this would be the e3sm.py
|
The other tests for |
Re: the ILAMB error, I ran with (Note that my note on #523 (comment) is to see if ILAMB 2.7 expands the zppy output and/or allows a simpler cfg. I can't really check that until I have 2.7 working in the first place). |
Okay I figured out the root cause of the Root CauseThis commit E3SM-Project/e3sm_diags@ As a result, in v2.10.0, the The FixThe fix is to change Other ThoughtsThis brings my idea again about testing these tools together, outside of E3SM Unified. We should consider more frequent releases and periodic testing before E3SM Unified releases. It would really cut down potential bugs appearing with E3SM Unified releases at the last second. It's not a good idea to try to rush out new package releases for "emergency" E3SM Unified releases, especially if the packages have a lot of changes. Also, the way |
Just an FYI that this run fails in v2.9.0 too, but the log file saves which makes it seems like it was working. UPDATE: Actually I didn't use NCO so it might be failing when I use the test On v2.9.0 output -- log file saves
|
Wow, that is a very insidious bug. So, it's just returning
Awesome, thanks!!
I absolutely agree. I should update the testing process as follows:
That's true. https://nvie.com/posts/a-successful-git-branching-model/ suggests merging patches into the user-facing releases AND the latest development branch. That is, only the bug fixes should be getting merged into user-facing code between the non-patch releases; we shouldn't be doing whole new releases of packages according to this particular workflow ideal.
I agree it's very convoluted. I haven't studied it enough to know if there's a simpler way to accomplish the same thing. |
I want to make sure I'm clear on how The latter, when set to It sounds like the former does something similar, but is not a parameter passed in by a user. It will have a value if all sets completed and otherwise will not. Is that right? |
Yeah we only want to return conda-forge/e3sm_diags-feedstock@79944cd
Notice in the code below that
I updated this logic in https://github.com/E3SM-Project/e3sm_diags/pull/770/files so that |
e3sm_diags v2.10.1rc1 is now released with these fixes: conda-forge/e3sm_diags-feedstock@79944cd |
Great, thanks @tomvothecoder! |
Re: Error 2, I made rubisco-sfa/ILAMB#85. |
@forsyth2 and @chengzhuzhang, it seems like we probably need to run
|
Re: Error 2, the issue does appear to be from not running |
Request criteria
Issue description
Testing
zppy
on Chrysalis, using E3SM Unified 1.9.2rc2, I run into the following errors on thecomplete_run
run. The errors appear to be similar on Perlmutter. Please note that there is not a newzppy
release for E3SM Unified 1.9.2. That is, these errors are occuring on azppy
version that was previously tested (for E3SM Unified 1.9.1).Error 1
e3sm_diags_atm_monthly_180x360_aave_environment_commands_model_vs_obs_*
:This is the job that makes sure the
environment_commands
parameter is working properly.1a
tests/integration/utils.py
had"diags_environment_commands": "source /home/ac.forsyth2/miniconda3/etc/profile.d/conda.sh; conda activate e3sm_diags_20231221"
, meaning it ran using a conda dev environment built off the latestmain
of E3SM Diags (E3SM-Project/e3sm_diags@9e14ff8)Since this case technically tests an unreleased version of E3SM Diags, I suppose this is fine to ignore for now.
1b
I then changed
tests/integration/utils.py
to use the version of E3SM Diags that was used in the other E3SM Diags jobs for this run. That is,"diags_environment_commands": "source /lcrc/soft/climate/e3sm-unified/test_e3sm_unified_1.9.2rc2_chrysalis.sh"
, which is the sameenvironment_commands
all the other jobs used. Looking at https://acme-climate.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment#e3sm-unified-1.9.2, that looks like that would be E3SM Diags v2.10.0 (E3SM-Project/e3sm_diags@0b7f9c7).Since this case tests the E3SM Diags version that is included in the upcoming Unified release, we should address this error.
1c
I then changed
tests/integration/utils.py
to use the version of E3SM Diags that was used in the other E3SM Diags jobs for this run. That is,"diags_environment_commands": "source /lcrc/soft/climate/e3sm-unified/load_latest_e3sm_unified_chrysalis.sh"
, which uses the latest official release of E3SM Unified. Looking at https://acme-climate.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment#e3sm-unified-1.9.1, that looks like that would be E3SM Diags v2.9.0 (E3SM-Project/e3sm_diags@a2d00eb).This works fine. That is expected since
zppy
had previously tested this version of E3SM Diags when we did the release for E3SM Unified 1.9.1.Potential sources of the bugs
1c -> 1b bug:
E3SM-Project/e3sm_diags@37d8019E3SM-Project/e3sm_diags@a0a3561E3SM-Project/e3sm_diags@633b52cE3SM-Project/e3sm_diags@0b7f9c71b bug -> 1a bug:
params_results
is not set (only set if successful)Error 2
ilamb_*
:I'm not sure if this is a bug with ILAMB itself or if there is simply a missing dataset (e.g., a dataset was deleted or the new version of ILAMB requires one that I'm not pointing to).
The text was updated successfully, but these errors were encountered: