-
Notifications
You must be signed in to change notification settings - Fork 18
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
All NCEPLIBS must have unit tests, and use continuous integration with GitHub actions #130
Comments
For CRTM, specifically, we're working on getting this done over the next month. We have multiple build support requirements due to CRTM being integrated in multiple model platforms. |
Almost all projects in NCEPLIBS already have CI with GitHub actions, which is great. But most of them are running no tests, which is the next area we need to improve. |
IP and IP2 have tests. But I don't know if they are working. I think @kgerheiser is working on this. |
I'm currently in the process of porting ip and ip2's tests to CMake |
I'll be providing a cmake build for CRTM within the "next couple of weeks". We have a code release coming up soon, once that's done, I'll work with the team to get linked to our releases and work out any build/test issues. |
To measure code coverage, compile like this:
|
Even though we didn't get to them during today's shortened NCEPLIBS meeting, here are my testing notes and tips: https://docs.google.com/document/d/1-vD24bjNcJTXGeu4rAHhJ9u_S7WcUmd75vX2wrFik88/edit?usp=sharing |
We will go over these at the next NCEPLIBS meeting. I look forward to it! |
We now have at least some unit tests, and good CI, on all active NCEPLIBS projects. I will close this issue. |
All NCEPLIBS repos must have testing. All must use CI with GitHub actions for testing.
A reasonably complex example, which builds and uses HDF5 and netCDF, can be found here:
https://github.com/NCAR/ParallelIO/blob/master/.github/workflows/a4.yml
The text was updated successfully, but these errors were encountered: