Recipes with issues discovered during the 2.10.0 release test runs

[bouweandela]

Tracking issue for the application of the broken recipe policy and release procedure.

All v2.10.0 test results are discussed in #3463.

Failing recipes identified during recipe testing for release of v2.10.0

• recipe_seaice_drift.yml recipe_seaice_drift.yml no longer runs #3243
• recipe_pysplot.yml recipe_psyplot.yml does not run with shapely 2 #3483

Failing recipes identified during recipe testing for release of v2.9.0

• recipe_julia.yml recipe_julia.yml produces unusable plot #2595

Failing recipes identified during recipe testing for release of v2.8.0

• recipe_check_obs Variable information from recipes overwritten by cmor table info when deriving custom variables ESMValCore#1388

Recipes that could not be run for v2.10:

Recipes that failed because the run took too long and/or required too much memory (suspected performance regression in Dask default scheduler)

recipe_climate_change_hotspot.yml
recipe_eyring06jgr.yml
recipe_eyring13jgr_12.yml
recipe_ipccwg1ar6ch3_fig_3_19.yml
recipe_ipccwg1ar6ch3_fig_3_42_a.yml
recipe_ipccwg1ar6ch3_fig_3_42_b.yml
recipe_lauer22jclim_fig5_lifrac.yml
recipe_lauer22jclim_fig3-4_zonal.yml
recipe_wflow.yml

Recipes that failed with HDF5 errors (suspected Levante/Lustre filesystem error)

recipe_collins13ipcc.yml
recipe_ipccwg1ar6ch3_atmosphere.yml
recipe_tebaldi21esd.yml