Skip to content
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

Replace pgi tests with new Nvidia compiler #1610

Closed
ekluzek opened this issue Jan 19, 2022 · 2 comments · Fixed by #1723
Closed

Replace pgi tests with new Nvidia compiler #1610

ekluzek opened this issue Jan 19, 2022 · 2 comments · Fixed by #1723
Assignees
Labels
testing additions or changes to tests

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jan 19, 2022

The PGI compiler was bought by Nvidia and as such the name of the compiler changes. The new compiler is available on Cheyenne, when it's available on izumi we'll want to change our izumi pgi tests to nvidia.

@ekluzek ekluzek added testing additions or changes to tests enhancement new capability or improved behavior of existing capability labels Jan 19, 2022
@billsacks billsacks removed the enhancement new capability or improved behavior of existing capability label Jan 20, 2022
@ekluzek ekluzek self-assigned this Apr 29, 2022
@ekluzek ekluzek added the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Apr 29, 2022
@ekluzek
Copy link
Collaborator Author

ekluzek commented Apr 29, 2022

Since, PGI is not working with NUOPC (it builds, but fails at runtime), this becomes more important. We don't have nvhpc on izumi still, so I think we should add a few nvhpc tests for cheyenne, and have cheyenne run intel, and gnu, nvhpc test suites. So this will change run_sys_tests adding nvhpc for cheyenne and removing pgi for izumi.

There's a limited amount of testing with nvhpc for CESM tags. I'm trying some tests in cesm2_3_alpha08d for CTSM, doing that should show us how feasible using nvhpc will be as a replacement for PGI.

For portability and robustness showing we can run on four compilers: intel, gnu, nag, and nvhpc is really good. Removing a compiler from the list might be OK, but worthwhile to keep four active compilers. Since, we also test on two machines that also tests a few different versions which is also helpful as well.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Apr 30, 2022

Because of #1733 the first test list for nvhpc should probably be small and only include one MPI test with DEBUG on (that will be an expected fail). But, tests with DEBUG off can be done as well as DEBUG on for mpi-serial cases.

@billsacks billsacks moved this from Needs Prioritization to Todo ~ weeks in CESM: infrastructure / cross-component SE priorities May 1, 2022
@billsacks billsacks removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label May 5, 2022
ekluzek added a commit to ekluzek/CTSM that referenced this issue May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing additions or changes to tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants