-
Notifications
You must be signed in to change notification settings - Fork 48
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
point to updated spack branch for ufs-related changes #407
point to updated spack branch for ufs-related changes #407
Conversation
@AlexanderRichert-NOAA error on macos-gcc for ufs-weather-model build:
See https://github.com/NOAA-EMC/spack-stack/actions/runs/3527458921/jobs/5916545108 |
@AlexanderRichert-NOAA I would like to merge this PR (and the spack PR) after #408 - that PR has its spack submodule PR merged already and just requires a final test on an HPC (doing now). CI tests are ok. You'll need the CI test bug fixes from #408 for your's to work. |
Sounds good to me.
…On Tue, Nov 29, 2022 at 1:34 PM Dom Heinzeller ***@***.***> wrote:
@AlexanderRichert-NOAA <https://github.com/AlexanderRichert-NOAA> I would
like to merge this PR (and the spack PR) after #408
<#408> - that PR has its
spack submodule PR merged already and just requires a final test on an HPC
(doing now). CI tests are ok. You'll need the CI test bug fixes from #408
<#408> for your's to work.
—
Reply to this email directly, view it on GitHub
<#407 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATVT32CYNJV435RJ6NCX6YTWKZZGNANCNFSM6AAAAAASIJTWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
One of the CI tests seem to have failed for no obvious reason: https://github.com/NOAA-EMC/spack-stack/actions/runs/3579347796/jobs/6023518324 - I am rerunning the test, and if successful I'll run the other canceled jobs manually, too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The submodule pointer update isn't correct, in fact it's not there at all. You are pointing to the jcsda_emc_spack_stack branch in the noaa-emc fork. In addition to updating .gitmodules
, you also need to commit the spack hash (which points to your branch ufs_hera_update
in your fork, hash is currently 5bfe007b90faa47c88daa6b1d56a5b3be7d2886f).
@AlexanderRichert-NOAA Something is wrong with this PR, I don't see the submodule pointer update for your spack PR. I see only the |
The issue with the CI tests is that spack now builds two versions of netcdf (shared) that only differ in their
|
I am seeing the same problem on my macOS with apple-clang, and on Cheyenne with Intel. Each time when building from the |
Hmm yep, that makes sense, I should have seen this coming. I think the play is to just take base-env out of ufs-weather-model-env and just have all the (non-python) UFS-related packages in one place, that way no conflicts over particular needs about netcdf variants etc. I'll update this shortly. |
I think I have a better solution in place, I messaged you in slack but I can also post it here. We can tag up quickly in google meet to discuss this if you like.
|
Merge remote-tracking branch 'origin/develop' into ufs_hera_update_nov2022
@AlexanderRichert-NOAA @mathomp4 I am happy with this PR and the associated spack PR. Please open this PR up for review, and if @mathomp4 could take another look at JCSDA/spack#192, please? |
Note on CI testing. CI tests all passed for 2b4a2a4 - including on my macOS (used the github label to kick off the self-hosted runner). |
@AlexanderRichert-NOAA I merged the spack PR. Please point your spack submodule pointer in this spack-stack PR back to the head of noaa-emc jcsda_emc_spack_stack (correct hash is 377817d) and revert the |
@climbfuji Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I verified the spack submodule hash, correct.
No description provided.