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

(closes #2601) Update nemo tests to nvhpc 24.11 #2631

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sergisiso
Copy link
Collaborator

No description provided.

Copy link

codecov bot commented Jun 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.88%. Comparing base (d74365a) to head (33046fa).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2631   +/-   ##
=======================================
  Coverage   99.88%   99.88%           
=======================================
  Files         357      357           
  Lines       49724    49724           
=======================================
  Hits        49668    49668           
  Misses         56       56           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@arporter
Copy link
Member

arporter commented Sep 6, 2024

I guess we should switch the nemo 4 tests to use the same Spack environment that you've got working for v5?

@nmnobre nmnobre force-pushed the 2601_nemo_to_nvhpc24.5 branch from 89a772e to 33046fa Compare November 29, 2024 14:31
@nmnobre nmnobre changed the title (closes #2601) Update nemo tests to nvhpc 24.5 (closes #2601) Update nemo tests to nvhpc 24.11 Nov 29, 2024
@nmnobre
Copy link
Member

nmnobre commented Nov 29, 2024

Right, it's seg faulting, that'll require more patience to fix. xD

@sergisiso
Copy link
Collaborator Author

Going to the integration test folder with the debugger it shows:

Program received signal SIGSEGV, Segmentation fault.
0x00007fffc0a4bd26 in __pgi_uacc_rb_find (T=0x3fd8f5c28f5c28f6, key=41560128) at ../../src/rbtree.c:348
warning: 348    ../../src/rbtree.c: No such file or directory
(gdb) bt
#0  0x00007fffc0a4bd26 in __pgi_uacc_rb_find (T=0x3fd8f5c28f5c28f6, key=41560128) at ../../src/rbtree.c:348
#1  0x00007fffc0a3d2f4 in __pgi_uacc_register_static (hostptr=0x27a2840 <_calendar_21_>, size=36,
    name=0x1156156 <.C313_..acc_data_constructor_24> "_calendar_21", flags=1280,
    pgi_cuda_loc=0x118ce50 <.C342_..acc_data_constructor_3>) at ../../src/static.c:50
#2  0x00007fffbca296fb in call_init (env=<optimized out>, argv=0x7fffffff9478, argc=1) at ../csu/libc-start.c:145
#3  __libc_start_main_impl (main=0x40be40 <main>, argc=1, argv=0x7fffffff9478, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffff9468) at ../csu/libc-start.c:376
#4  0x0000000000408225 in _start ()

@sergisiso
Copy link
Collaborator Author

sergisiso commented Nov 29, 2024

Also the log shows many nvfortran-Warning- The -gpu=[no]managed option is deprecated; please use -gpu=mem:managed or -gpu=mem:separate instead", aren't these updated in this PR?

Ah no, this lives inside the nemo arch/* folder

We are also linking /home/aporter/NEMO/xios_trunk which may use a older/incompatible compiler - also with a different MPI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants