-
Notifications
You must be signed in to change notification settings - Fork 51
Re-enabling robust integration test. #1729
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
base: develop
Are you sure you want to change the base?
Conversation
|
Evaluation currently breaks with (CC @SavvasMel @iluise): |
|
The parameters also need to be re-tuned. ERA5 converged too slowly, but using a very limited number of channels as before also let to unreliable convergence for NPP-ATMS. |
I want to have a more general discussion about the goals of our testing including also Tim if possible. I think we should separate testing the control and data flow from testing for convergence:
|
For ERA5 we had a config that tests/tested convergence (that it starts to converge, but that's enough) in less than 5 min on all platforms. So I still don't fully see why we should have multiple tests. |
Description
Re-enabling robust integration test
Issue Number
Closes #1712
Checklist before asking for review
./scripts/actions.sh lint./scripts/actions.sh unit-test./scripts/actions.sh integration-testlaunch-slurm.py --time 60