-
Notifications
You must be signed in to change notification settings - Fork 19
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
ClimaCoupler downstream test is failing #3165
Comments
Yes, we are aware of this and mark #3150 as a breaking change. But in general what should we do when this test is failing? |
When this test is failing, this means that Breaking changes will indeed break this test, but sometimes it is easy to ensure compatibility with previous versions. A pattern you might consider is
But this should not become a burden, so just do it if it is easy. |
But we can't merge the ClimaCoupler PR until the atmos is updated, so the downstream test will still fail. Should we just tag a minor release as soon as we have breaking changes? But then we will have many releases... |
If it is easy, you can support both versions. If not, it is not a big deal, just wait until you release ClimaAtmos. This test is mostly to give us an indication of what might go wrong, but it is not a strict test. |
@Sbozzolo This is fixed here: CliMA/ClimaCoupler.jl#889. We may be able to close this issue. In this instance the solution was to update the coupler interface for compatibility with the latest atmos breaking changes. |
https://github.com/CliMA/ClimaAtmos.jl/actions/runs/9753198215
This is probably related to some recent changes in insolation. @szy21 @cmschmitt519
The text was updated successfully, but these errors were encountered: