Skip to content
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

Out-of-schedule ESMValTool date for developer discussion about testing strategy - DATE FIXED (Thursday Oct 14, 2pm-5pm CEST) #2259

Closed
hb326 opened this issue Aug 6, 2021 · 7 comments

Comments

@hb326
Copy link
Contributor

hb326 commented Aug 6, 2021

Hey all,
after we had some problems with the recipe testing lately, and after we had a brief discussion about a possible ESMValTool testing strategy at the last monthly meeting, we decided that it would be a good thing to set aside some time to be able to discuss this in detail.
So there will be a half-day out-of-schedule ESMValTool developers meeting to talk about a testing strategy. Please indicate your availability below. Thanks!

https://terminplaner4.dfn.de/KzhsW6Ruac8OtByP

@ESMValGroup/esmvaltool-developmentteam
@ESMValGroup/esmvaltool-coreteam

The doodle will be open until the first week of September.

@hb326
Copy link
Contributor Author

hb326 commented Aug 31, 2021

Hey all @ESMValGroup/esmvaltool-developmentteam @ESMValGroup/esmvaltool-coreteam,
please don't forget to fill out the poll, so that we can set a date and time for the disucssion about the recipe testing.

Thanks!!

@schlunma schlunma pinned this issue Sep 2, 2021
@hb326 hb326 changed the title Out-of-schedule ESMValTool date for developer discussion about testing strategy Out-of-schedule ESMValTool date for developer discussion about testing strategy - DATE FIXED (Do Oct 14, 2pm-5pm CEST) Sep 7, 2021
@hb326 hb326 changed the title Out-of-schedule ESMValTool date for developer discussion about testing strategy - DATE FIXED (Do Oct 14, 2pm-5pm CEST) Out-of-schedule ESMValTool date for developer discussion about testing strategy - DATE FIXED (Thursday Oct 14, 2pm-5pm CEST) Sep 7, 2021
@hb326
Copy link
Contributor Author

hb326 commented Sep 7, 2021

Hey all @ESMValGroup/esmvaltool-developmentteam @ESMValGroup/esmvaltool-coreteam,
we have a date and time for the out-of-schedule ESMValTool discussion about testing strategy:
Thursday Oct 14, 2pm-5pm CEST

Please mark this date in your calendars. We will send around information about the meeting details closer to the meeting date.

@hb326
Copy link
Contributor Author

hb326 commented Oct 7, 2021

Hey all @ESMValGroup/esmvaltool-developmentteam @ESMValGroup/esmvaltool-coreteam ,
just a brief reminder that we have the ESMValTool half day meeting about the testing strategy next Thursday afternoon!
We will post the link to access the meeting here next week closer to the meeting day.

For now, you can familiarize yourself with the recipe testing problem by looking at the following issues:

If you have any ideas about the testing strategy or know about an issue that could be relevant, please post them in this issue here.
Thanks!

@bouweandela
Copy link
Member

@remi-kazeroni
Copy link
Contributor

remi-kazeroni commented Oct 14, 2021

Here was the link for the meeting taking place today, 14:00-17:00 CEST.

@remi-kazeroni
Copy link
Contributor

The summary of the meeting can be found in the three issues listed below. During the meeting, we have decided to considerer three different categories of automatized recipes testing performed at different frequencies (from most to least frequent ones):

  1. (#1361) run special recipes on a nightly basis to test the latest changes in the ESMValCore and check if and how these would break recipes. The development of such test recipes for the core will be discussed at the November workshop (ESMValTool workshop Nov 2021 #2311)
  2. ([recipe testing strategy] Testing recipes on a weekly basis #2346) run batch of recipes in an automatized way on a weekly basis to check if these are affected by the latest changes in the Core. This would help to identify possible problems earlier than close to a release.
  3. ([recipe testing strategy] Testing all recipes before a release #2345) run all recipes prior to a release in an automatized way to check whether recipes work fine with the latest versions of the Core and the Tool.

@valeriupredoi
Copy link
Contributor

many thanks for the notes taken during the meeting and summary @remi-kazeroni 🍺

@valeriupredoi valeriupredoi unpinned this issue Oct 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants