-
Notifications
You must be signed in to change notification settings - Fork 129
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
Recipe testing for release 2.8.0 - Core release candidate rc1 #3076
Comments
Overview of the resultsNumbers of successes and failuresThe first round of recipe testing produced:
For comparison, we released ESMValTool 2.7.0 with 4 non-working recipes (this could have been 8 if we used a stricter policy on missing data as done for this round of testing) Overview webpage and path to data
Note: I will now write three more posts to this issue for each category of failures (missing data, diagnostic issues, preprocessor issues) and provide more details about failures and lists of affected recipes. Please do not use this issue to comment on single recipe failures but rather open a separate issue, linking to this one. This issue is intended to provide a general overview or discuss recurring problems. More info and tagging the community soon 👍 |
@remi-kazeroni great work on this, bud! I see some manifestations of #3061 - so that might not be just a mocking test error; maybe @bouweandela has some time to look at, at least, anav failure 🍺 |
Recipe failures due to missing data or files or data issues
|
Recipe failures due to diagnostic errors
|
Recipe failures due to preprocessor errors
|
Hi @ESMValGroup/esmvaltool-developmentteam and @ESMValGroup/esmvaltool-recipe-maintainers, the results from the first round of recipe testing for the release of ESMValTool and ESMValCore v2.8 are now available. See summary and link to the overview webpage in this #3076 (comment) above. It would be great if you could take a look at the results of your favourite recipes and help fixing the failing ones. In such cases, please assign yourselves in the tables above and if possible open separate issues to discuss the problems. Feel free to comment here if you have noticed other problems with the recipe output. There are 3 main categories of failures: Any help will be greatly appreciated 👍 |
@remi-kazeroni one thing you should tell the users that will be running their recipes is to deactivate the esmvalcore 2.7.* pin in environment.yml and make it either 2.8.* or remove it completely, and to activate the rc channel 👍 |
hang on, we have an issue with the Tool env picking up Core 2.8.0rc1 off the rc channel/label - am looking into this atm 👍 |
@remi-kazeroni my apologies - for the autoassess soilmoisture recipe, I plopped the clima files at |
Thanks for checking, good to know it runs fine 👍 We have started to discuss how to handle this recipe in the issue on the broken recipe policy #3065 (see this #3065 (comment)). If the clima files cannot be publicly accessed and if that access cannot be documented, we will always have trouble testing such recipes for releases. Remember that we have discussed a lot already to avoid these manual steps where the release manager would need to search for extra files to run particular recipes. This makes the release process too complicated otherwise. I think you have a PR that aims at simplifying the description of the release process: #3032 (I'm going to push it to the finish line soon) 👍 |
totally with you on that, bud! ah that #3032 - had forgotten about it 😁 BTW great work streamlining it, such a socialist/community PR ⚒️ |
A quick try to see if I can solve the hype issue detected in #3076
Thanks everyone for your support with fixing recipes! Most failed recipes have received some attention and many of them got fixed already. That's great news for the upcoming release 👍 Up to now, it seems that 2 recipes have unfortunately not received attention: File "/home/b/b309192/ESMValTool/esmvaltool/diag_scripts/arctic_ocean/utils.py", line 223, in get_cmap
cm.register_cmap(cmap=LinearSegmentedColormap(
File "/work/bd0854/b309192/soft/mambaforge/envs/tool_280rc1/lib/python3.10/site-packages/matplotlib/_api/deprecation.py", line 200, in wrapper
return func(*args, **kwargs)
File "/work/bd0854/b309192/soft/mambaforge/envs/tool_280rc1/lib/python3.10/site-packages/matplotlib/cm.py", line 263, in register_cmap
_colormaps.register(cmap, name=name, force=override_builtin)
File "/work/bd0854/b309192/soft/mambaforge/envs/tool_280rc1/lib/python3.10/site-packages/matplotlib/cm.py", line 136, in register
raise ValueError(
ValueError: A colormap named "cubehelix3" is already registered. Traceback (most recent call last):
File "/home/b/b309192/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 817, in <module>
main(config)
File "/home/b/b309192/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 755, in main
_plot_single_map(plot_path_mod, tau_ctotal,
File "/home/b/b309192/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 660, in _plot_single_map
_fix_map(_ax)
File "/home/b/b309192/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 278, in _fix_map
plt.gca().outline_patch.set_visible(False)
AttributeError: 'GeoAxes' object has no attribute 'outline_patch' If you happen to know their maintainers or colleagues/friends or if you have encountered similar diagnostic issues recently, you are most welcome to jump in here and help us getting the recipes fixed for the upcoming release. Otherwise these would be marked as broken in ESMValTool v2.8. |
@remi-kazeroni hold on tight buddy, Carvalhais will get a solution in the next few minutes, I know exactly what's up there |
Carvalhais needs to get back to the other patches - @zklaus fixed that for when we pinned Matplotlib last release, see #2886 (comment) - now we need to revert that, I'll PR it now |
Carvalhais14 fixed here #3111 |
Hi, I looked at the recipe_arctic_ocean log, and apparently the Unfortunately, I'm not able to run any test at the moment. The Norwegian national data storage is migrating all data to a new location, and have closed down access for some time. |
Hi @TomasTorsvik, thanks very much for taking a look and your suggestion! It would be great if you or someone could make these modifications available in a branch and open a (draft) pull request with that. This would then ease the testing for developers like me with access to all necessary data at DKRZ. Note that you could also make use of our bot directly from that PR (see doc). This would allow you to request a fresh installation of ESMValTool and a test run at DKRZ directly via the PR. |
Thanks everyone for you help and support with fixing recipes! All cases have now been addressed. I'm closing this and will open tomorrow another issue for the second and last round of testing (currently ongoing) where the community will be asked to take a look at recipe output and status of the comparison with results from the previous release. |
legend @remi-kazeroni 🎖️ Hopefully the next (and last) round will be a cake walk 🍰 |
This issue documents the round of recipe testing performed using the Core release candidate
v2.8.0rc1
.Release process
System and settings
conda
/mamba
Git branches and state
Tue 7 Mar 16:06:43 CET 2023
Installation and environment
Config user file
Main options: all default except
search_esgf: when_missing
ESMValTool version
Environment file
tool_280rc1.txt
Compute resources used
On DKRZ-Levante
Note: no output comparison will be done for this round of testing. The main purpose is to identify issues with the Core and start fixing failing diagnostics. Results and overview webpage will be posted in a later post.
The text was updated successfully, but these errors were encountered: