-
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
Update CircleCI to use both gfortran and ifort #831
Conversation
Time to ask CircleCI Forum for help... |
Woooo! I think I got it. We'll find out... |
I await the inevitable discussion with @tclune on the commits I made to |
Timings from CircleCI: MAPL Build Test:
GEOSgcm Build:
Go Intel, I guess! |
Throwing on a blocker until @tclune can see and comment. |
Closes #830 |
Some cost analysis of this PR using 40 credits/min on
The total here is:
CircleCI reports 1761 so not too far off. |
Okay. Just did a test using
CircleCI reports 796 credits used, again, about right. Well, that's obviously better. (I also turned off the FV3 tests as they are probably not that necessary.) |
Getting close to undrafting. Frankly, I don't think we miss anything by not building/running GEOSfvdycore, and I think the ability to build/test both GNU and Intel is more important. I'll see what @tclune says. |
Decided to try adding the GEOSadas to the CI. But it looks like we are missing something for MKL in the Docker image. Let's figure that out. |
So, it turns out we can't quite do GEOSadas with MAPL yet. The reason is that GEOSadas is now "behind" GEOSgcm in a crucial way: Baselibs. So, time to make a PR... |
PR to GEOSadas submitted: GEOS-ESM/GEOSadas#103 |
This PR enables both gfortran and ifort builds of MAPL and GEOSgcm
Closes #830