Hello Bing, It appears that the failure is from an invocation of `mpiexec` in the parallel test script. This doesn't indicate a netcdf failure, per se, but rather something has failed to run when trying to execute the mpiexec program. You should be able to ignore it insofar as netcdf goes, but it may be indicative of a problem with your parallel/mpi environment. I hope this helps, -Ward > Hi, > > This is what I got when I tried to install netcdf4.3.3 on a linux > cluster. Are there any reasons or solutions for this failure. > > By the way, even with this only failure, I can still finish the final > installation. Just not sure if this would lead to further problems. > > Best, > Bing > > > ============================================================================ > Testsuite summary for netCDF 4.3.3-rc3 > ============================================================================ > # TOTAL: 56 > # PASS: 55 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > ============================================================================ > See nc_test4/test-suite.log > Please report to address@hidden > ============================================================================ > > > =============================================== > netCDF 4.3.3-rc3: nc_test4/test-suite.log > =============================================== > > # TOTAL: 56 > # PASS: 55 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: run_par_test.sh > ===================== > > > Testing MPI parallel I/O without netCDF... > address@hidden HYDT_bsci_launcher_pbs_init > (tools/bootstrap/external/pbs_init.c:33): tm_init() failed with TM error 17005 > address@hidden HYDT_bsci_init (tools/bootstrap/src/bsci_init.c:152): launcher > init returned error > address@hidden main (ui/mpich/mpiexec.c:173): unable to initialize the > bootstrap server > FAIL run_par_test.sh (exit status: 255) > > > Ticket Details =================== Ticket ID: BHZ-830564 Department: Support netCDF Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.