Skip to content

Recipe test results for v2.13.0 #4157

@jlenh

Description

@jlenh

See updates at #4157 (comment)


@ESMValGroup/esmvaltool-developmentteam Here is an overview of the tests performed for the v2.13.0 release. The results are summarized in /home/b/b381312/projects/outputs_rc1/run1 (waiting for access to the VM).

Here is the conda environment: esmvaltool-core_v2.13.0rc1.txt

More details on the errors are added gradually!

Recipe running session 2025-08-22

136 out of 180 recipes ran successfully, 38 recipes failed. You can find below the errors summarized.

Recipes that failed because the diagnostic script failed (13 out of 180)

Recipes that failed because of missing data (5 out of 180)

Recipes that failed because the run took too long (11 out of 180)

  • recipe_climate_change_hotspot.yml
  • recipe_eyring06jgr.yml
  • recipe_eyring13jgr_12.yml (preprocessor creates output but then hangs for unknown reasons, diagnostic script is not called)
  • recipe_flato13ipcc_figures_926_927.yml
  • recipe_ipccwg1ar6ch3_fig_3_19.yml
  • recipe_lauer22jclim_fig5_lifrac.yml (that's a known problem as extract_levels is very slow)
  • recipe_miles_block.yml
  • recipe_miles_eof.yml
  • recipe_miles_regimes.yml
  • recipe_wenzel14jgr.yml
  • recipe_wenzel16jclim.yml

Recipes that failed because they used too much memory (2 out of 180)

  • recipe_lauer22jclim_fig3-4_zonal.yml (that's a know problem as the bot does not have enough memory)
  • recipe_ref_trend_regions.yml

Recipes that failed of other reasons or are still running (13 out of 180)

Recipes that never ran (1 out of 180)

  • recipy_capacity_factor.yml

Sub-issues

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions