This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Dennis, Below is the output from run_pnetcdf_test.sh with set -x: vagrant@t64pnet:~/netcdf-working/nc_test$ ./run_pnetcdf_test.sh > + set -e > + echo > + echo Testing file created with pnetcdf is modifiable with netCDF... > Testing file created with pnetcdf is modifiable with netCDF... > + ./tst_pnetcdf > *** Testing bug fix with changing pnetcdf variable offsets...ok. > *** Tests successful! > + set -x > + mpiexec -n 4 ./tst_parallel2 > 4 0.000329018 6.22459e+06 > Sorry! Unexpected result, tst_parallel2.c, line: 170 > Sorry! Unexpected result, tst_parallel2.c, line: 170 > -------------------------------------------------------------------------- > mpiexec has exited due to process rank 2 with PID 10780 on > node t64pnet exiting improperly. There are two reasons this could occur: > 1. this process did not call "init" before exiting, but others in > the job did. This can cause a job to hang indefinitely while it waits > for all processes to call "init". By rule, if one process calls "init", > then ALL processes must call "init" prior to termination. > 2. this process called "init", but exited without calling "finalize". > By rule, all processes that call "init" MUST call "finalize" prior to > exiting or it will be considered an "abnormal termination" > This may have caused other processes in the application to be > terminated by signals sent by mpiexec (as reported here). > -------------------------------------------------------------------------- Running mpiexec -n 2 ./tst_parallel2 is successful. If I allocate 4 CPU's to the VM I'm testing on, 'mpiexec -n 4 ./tst_parallel2' works. Working with netcdf-4.3.0, I don't see the reliable failure when specifying more processes than processors. -Ward address@hidden> wrote: > New Staff Reply: make check failed > > We have a problem here. Ward says he duplicated the problem, > but using the current github version, I cannot duplicate the problem. > > Could one or both of you do the following. > 1. edit run_pnetcdf_test.sh > and insert the command 'set -x' immediately > after the '#!/bin/sh' line. > 2. Enter the nc_test directory and > execute make check > 3. report back the complete output. > > =Dennis Heimbigner > Unidata > > > Ticket Details > =================== > Ticket ID: MRB-844393 > Department: Support netCDF > Priority: Normal > Status: Closed > Link: > https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=24086 > > Ticket Details =================== Ticket ID: MRB-844393 Department: Support netCDF Priority: Normal Status: Closed