-
Notifications
You must be signed in to change notification settings - Fork 6
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
add slurm support for err_exit #69
Conversation
Thanks for your view, @edwardhartnett! What should I do to get this PR move forward? |
@Hang-Lei-NOAA I got a question about moving this PR forward. Is anything else needed for it? Thanks! |
@matthew Pyle - NOAA Federal ***@***.***> The C test error
should be fixed. Then you can merge it to the repository.
…On Fri, Dec 8, 2023 at 1:52 PM MatthewPyle-NOAA ***@***.***> wrote:
@Hang-Lei-NOAA <https://github.com/Hang-Lei-NOAA> I got a question about
moving this PR forward. Is anything else needed for it? Thanks!
—
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWSMFDA7S5TJSTDB7EX7K3YINOU3AVCNFSM6AAAAAA7LYD5U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGY3DMOBTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@Hang-Lei-NOAA I think the C test error is not due to the change in this PR. This failed test is for Intel. Do we have an Intel compiler available in Github? Upon further checking, it looks like the process of downloading and installing an Intel compiler failed. If someone can rerun the tests, it may pass? |
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.
a suggestion to work this logic in the context of SENDECF
Co-authored-by: Rahul Mahajan <aerorahul@users.noreply.github.com>
Thanks, Rahul! Just committed the change as suggested. |
There might be something wrong with the C Intel test setting which is out the scope of this PR. Could someone check and fix it? Thanks! |
Please check to see the intel workflow:
under .github/workflows/Intel.yml
If the C test version have any comflicited parts with your commit.
…On Mon, Dec 11, 2023 at 11:40 AM Guoqing Ge ***@***.***> wrote:
There might be something wrong with the C Intel test setting which is out
the scope of this PR. Could someone check and fix it? Thanks!
—
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWSMFGJYBODHXTRRO4WBRDYI4ZQRAVCNFSM6AAAAAA7LYD5U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJQGQ2TCMJUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @Hang-Lei-NOAA Thanks for the information. I only made a change in one BASH file which does not involve any C/C++ codes and I did not touch any other codes. From my understanding, the current code base before my PR cannot run this C Intel test. |
@guoqing-noaa |
I am so sorry that I had used the github "commit suggested changes" button and did not check the final result. Thanks a lot for help. Now it is fixed. |
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.
looks good.
@edwardhartnett @Hang-Lei-NOAA |
@guoqing-noaa
However, I think that will break the |
Let's wait for Alex's comment, since he did the last change in CI test for
spack.
…On Mon, Dec 11, 2023 at 2:13 PM Rahul Mahajan ***@***.***> wrote:
@guoqing-noaa <https://github.com/guoqing-noaa>
Please replace this
<https://github.com/NOAA-EMC/NCEPLIBS-prod_util/blob/7ed3e7aa92c1889349fd4cab3a47a0a5bb74a3ca/.github/workflows/Intel.yml#L38>
with the following and push again.
sudo apt-get install intel-oneapi-dev-utilities intel-oneapi-mpi-devel intel-oneapi-openmp intel-oneapi-compiler-fortran-2023.2.1 intel-oneapi-compiler-dpcpp-cpp-and-cpp-classi
However, I think that will break the icx and ifx modes.
@AlexanderRichert-NOAA <https://github.com/AlexanderRichert-NOAA> Can we
get some assistance in getting this PR through?
—
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWSMFHRJOWMVEJHWPQOBHLYI5LMJAVCNFSM6AAAAAA7LYD5U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJQG4YTSOBRGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Indeed, add '-2023.2.1' to the intel fortran and c compiler packages in the apt install line. This won't/shouldn't break the icx/ifx workflow, it just won't be using the absolute most recent versions. |
Thanks all. I will try to make the CI test change suggested by Rahul. |
@guoqing-noaa |
Thanks a lot for your help! @aerorahul @MatthewPyle-NOAA @Hang-Lei-NOAA @AlexanderRichert-NOAA |
@aerorahul @Hang-Lei-NOAA Can you make a new tag? I can provide this to @climbfuji |
@edwardhartnett has a draft for v2.2 started. Perhaps he can finish that and include this in that release. |
@edwardhartnett Will we have a new tag in the next 1 or 2 days? |
Thanks we have the new tag 2.1.1 in spack-stack since yesterday |
Sorry I've been slow to respond, I've been at the AGU. Do you want a new release of prod_util? |
Resolve issue #68