Update CMIP6 tables to 6.9.32

[jvegreg]

As request by @bouweandela in #704

Tasks

• Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
• This pull request has a descriptive title that can be used in a changelog
• Add unit tests
• Public functions should have a numpy-style docstring so they appear properly in the API documentation. For all other functions a one line docstring is sufficient.
• If writing a new/modified preprocessor function, please update the documentation
• Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
• Codacy code quality checks pass. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
• Please use yamllint to check that your YAML files do not contain mistakes
• If you make backward incompatible changes to the recipe format, make a new pull request in the ESMValTool repository and add the link below

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.

---

Closes #704

[jvegreg]

The tests are failing because of an error of pytest. They run locally without issue

[bouweandela]

Thanks! I created a pull request to fix the failing tests: #707.

[jvegreg]

Codacy analysis was not setup for this branch. I just did it

[bouweandela]

Looks good! @mattiarighi Could you please test?

[mattiarighi]

I think we can test this once we make the final run of all recipes.

[bouweandela]

Just for clarity, do we want to have this included in v2.0.0? We've had problems in the past when updating the CMOR tables, because the format changed, so I'm not sure if it's safe to include an update this late.

[jvegreg]

Just for clarity, do we want to have this included in v2.0.0? We've had problems in the past when updating the CMOR tables, because the format changed, so I'm not sure if it's safe to include an update this late.

My answer will be yes, but not as much as to block v2.0 release. I think we can manage to do it, as it will be tested thoroughly when running all the recipes. Also, if we detect non trivial issues, reverting this change is easy and safe, as no other commits will modify the affected files.

[bouweandela]

I think we can manage to do it, as it will be tested thoroughly when running all the recipes.

The main question then is, when are we going to do this? After the ESMValCore v2.0.0 release on July 20 or before it? I have tried to run about 20 recipes on the esmvaltool VM, but have no time to continue that testing before the release. @mattiarighi What are your plans in this?

[mattiarighi]

Ideally all recipes should work with the released version.
If we share the effort, I think it's doable to test all of them before the release.

Concerning the tables, it's probably better to include this at a later stage.

[jvegreg]

Concerning the tables, it's probably better to include this at a later stage.

Ok, just beware that some model names have changed between versions. It is possible that you find errors because of this in CMIP6 recipes if the data in DKRZ has been updated

[bouweandela]

Merging this now, so it will be included in the next release.