-
Notifications
You must be signed in to change notification settings - Fork 32
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
Question on building gdasapp on orion #1418
Comments
@DavidNew-NOAA recently updated the GDASApp/test/gw-ci/CMakeLists.txt Line 240 in d6097af
gw-ci ctest.
I gave up on Orion ages ago. I ony run on |
@guillaumevernieres, yes, I have the option ON, and when I run |
I do hit an issue loading gdasapp modules on hera as well:
|
An on hercules:
|
@shlyaeva: We need to build GDASApp inside g-w in order for g-w based GDASAApp ctests to be active. Since I usually run g-w based ctests, I begin my development cycle with your option 1. If subsequent development requires me to make changes to GDASApp source code or ctests, I then flip over to option 3 to rebuild GDASApp. As a test I cloned GDASApp Hera
Hercules
Orion
|
Thank you @RussTreadon-NOAA, that's very helpful! On hercules, if I do
But if I follow what you do, and do
Not sure why, but since this resolves this for me, I'm closing the issue. Thank you! |
@shlyaeva , I replicated the behavior you observed by adding A few google searches and trial and error stumbled across the following change to
With this change to
I also tried |
@RussTreadon-NOAA nice, thank you for looking into this and finding a fix! 🎉 |
Work for this issue will be done in feature/modulefiles |
Using If we focus on Orion,
In contrast,
Replacing
and executing
With I can not find detailed documentation on As a test try the following change in
With this change in place,
Is this an acceptable solution? What do you think? Tagging @CoryMartin-NOAA , @DavidNew-NOAA , @danholdaway , @guillaumevernieres , @shlyaeva for awareness |
I'm okay with this |
My assumption is that I can build gdasapp 3 ways:
global-workflow/sorc/build_all.sh -gu
(which rebuilds everything in gw)global-workflow/sorc/gdas/build.sh
(which rebuilds everything in gdasapp)cd global-workflow/sorc/gdas/; module use modulefiles/GDAS; module load $machine.$comp; cd build/gdas; make -j12
I think I have successfully used many combinations of these three ways with different machines (orion, hera, hercules) at different times in the past month, but now I'm struggling to build on orion with 2 and 3. I wanted to check if that's expected behavior currently, or whether I'm doing something wrong.
For 2, the code builds, but only a small subset of the tests is available in gdas build directory (none of the gw-ci tests are there).
For 3, I fail to load modules on orion with the following error:
If I naively remove the offending module, I get
and I think I have seen a similar message on a different platform before (probably hera? but I'm not sure).
Am I doing something incorrectly when I try to build with 2 and 3 on orion? Is there a recommended way for the quickest rebuild of gdasapp (without rebuilding everything from scratch)?
The text was updated successfully, but these errors were encountered: