-
Notifications
You must be signed in to change notification settings - Fork 37
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
Building hpc-stack-nco branch in ubuntu 20.04 container with gcc 9 and mpich 3.3.2 #71
Comments
Maybe because ubuntu is using dash instead of bash as default shell? Just a wild guess. |
Just to be clear, this is an issue in the branchfeature/hpc-stack-nco and not with develop. |
Yeah, in ubuntu /usr/bin/sh is linked to /usr/bin/dash.
But I doubt that sh is able to handle double bracket notation "[[" either.
…On Tue, Nov 17, 2020 at 5:06 PM Dom Heinzeller ***@***.***> wrote:
Maybe because ubuntu is using dash instead of bash as default shell? Just
a wild guess.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANUTPO3FVQKAXR4RC732LPLSQLXXNANCNFSM4TYY265Q>
.
|
I usually relink /usr/bin/sh to /usr/bin/bash - can you try? |
That should work. But the second issue still remains: missing: NetCDF_Fortran_LIBRARY NetCDF_Fortran_INCLUDE_DIR |
Why is this not raised in the CI which uses ubuntu 20.04? |
It's possible that the CI version does this relinking, too - specifically to address the dash shortcomings. I remember having seen something like this in the past. |
No such special treatment in the hpc-stack workflow. |
I am concerned that a branch that did not pass CI or any kind of review went into the UFS PR. |
Current CI is using a container that does not use hpc-stack. |
Exactly my point. |
If hpc-stack-nco was built on NOAA machines successfully, that's fine, as far as ufs-weather-model is concerned, I think. I am just encountering an issue trying to build hpc-stack-nco branch in a container. |
I am not sure if any of this is helpful to solve the issues we have right now. I'll try something different. Minsuk, these variables are usually set by FindNetCDF.cmake - do you have the ominous |
|
That didn't do it. Same error without |
This must be resolved before #72 @MinsukJi-NOAA how do we reproduce this error on a regular ubuntu workstation? |
@edwardhartnett, the 'steps to reproduce' above assumes you have docker installed on your ubuntu workstation. |
Can we do a 1.1 release of hpc-stack without resolving this issue? Or must this issue be resolved before the release? @kgerheiser would like to do a release tomorrow or the next day... |
@edwardhartnett , this issue is with feature/hpc-stack-nco branch, and not with develop branch. So, if #72 is not merging the feature/hpc-stack-nco into develop, I don't see why this needs to be resolved before 1.1 release. |
OK, hpc-stack-nco is indeed going to be merged. So does this need to be resolved before the imminent 1.1.0 release? |
I don't see how it will be merged in its current state. We can discuss this later today. |
We believe the develop branch will work in the ubuntu container. Can you try this please. |
The develop branch worked in ubuntu container when I tested it two days ago. I was trying to use hpc-stack-nco branch because it has upp in it (which the weather model is using now). If I use the develop branch, and specify upp in config files, would that work? |
UPP has been added to the develop branch |
That's great! I will test the latest weather model in an ubuntu 20.04 container, and report the outcome. |
I verified that this works by installing hpc-stack/develop in ubuntu 20.04 container and running ufs-weather-model restart unit test. |
Latest develop branch failed to build in ubuntu 20.04. Error messages are:
I did not write down which version passed my test on 11/20/2020, but I am guessing either 10a8431 or 941250a. I can find out which commit is the culprit if it is helpful. |
The issue is that it's building two UPP's, the one with the commit They have the same Fortran module names ( The solution is to disable building Maybe we should disable that in the stack file that you are using? Is it |
Thank you @kgerheiser . No, I don't think so. I am building with nceppost disabled in |
It works fine when you build in a hierarchical structure with lmod, but when installing in a flat structure, like in a container, the names conflict. |
I was able to build the latest develop branch with nceppost disabled in stack_ufs_weather_ci.yaml. |
Describe the bug
Using build_stack.sh fails to install hpc-stack-nco in ubuntu 20.04 container
To Reproduce
./build_stack.sh -p /home/builder/opt -c config/config_custom.sh -y config/stack_custom.yaml
Build fails with "[[: not found" error message.
Change all lib/build_*.sh from #!/bin/sh to #!/bin/bash
Repeat above steps and build fails with:
-- Could NOT find NetCDF_Fortran (missing: NetCDF_Fortran_LIBRARY NetCDF_Fortran_INCLUDE_DIR)
CMake Error at src/flib/CMakeLists.txt:275 (message):
Must have PnetCDF and/or NetCDF Fortran libraries
-- Configuring incomplete, errors occurred!
See also "/home/builder/hpc-stack/pkg/pio-2.5.1/build/CMakeFiles/CMakeOutput.log".
BUILD FAIL! Lib: pio Error:1
System:
Ubuntu 20.04, gcc 9, mpich 3.3.2
The text was updated successfully, but these errors were encountered: