Run a nightly test with the development version of dependencies

bouweandela commented 2 months ago

Description

Add a nightly test with development versions of upstream packages, to signal problems early. As agreed at the tech lead team meeting on 2024-07-02.

Other changes in this pull request:

update the orbs to the latest versions
write logs also to the terminal for easier viewing

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🧪 The new functionality is relevant and scientifically sound
[x] 🛠 This pull request has a descriptive title and labels
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Changes are backward compatible
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 The list of authors is up to date
[x] 🛠 All checks below this pull request were successful

To help with the number pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

codecov[bot] commented 2 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.64%. Comparing base (7291433) to head (dfcb585).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #2478 +/- ## ======================================= Coverage 94.64% 94.64% ======================================= Files 249 249 Lines 14114 14114 ======================================= Hits 13358 13358 Misses 756 756 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

valeriupredoi commented 1 month ago

ie what I meant by issues: both installation issues resulted from dependency conflicts (unevened environments yet to be evened at release times by all those guys); also scientific/numerical/deprecation troubles eg iris depends on cartopy, but cartopy decides to change something in their dev code, iris dev picks up the conda cartopy so all's fine, but when dev cartopy is installed, iris barfs, and we don't know who needs to fix what - we really don't want to start acting like the US Marines going everywhere to solve everyone else's problems :grin:

ehogan commented 1 month ago

Thanks @bouweandela! 🥳

The only question I have is: I think we're bound to catch a few too many issues if we test against the dev versions of all those packages, and maybe we get lost in understanding what's going on, should we not just use it for iris, as @ehogan initially suggested in the TLT minutes?

I had this same question 😊 We could see how it goes testing all these packages and if it gets too noisy we could review? 🤔

bouweandela commented 1 month ago

We could see how it goes testing all these packages and if it gets too noisy we could review? 🤔

That sounds like a great plan!

valeriupredoi commented 1 month ago

I had this same question 😊 We could see how it goes testing all these packages and if it gets too noisy we could review?

@ehogan that's exactly why I approved, but in light of me last comment, I think this may go downhill at some point :grin:

ESMValGroup / ESMValCore