Lorenzo, > I checked the files run_tests.sh and run_nc4_tests.sh in the path: > > .../libmesh_root/contrib/netcdf/4.3.1/ncgen3/ > > and they match with the sources in github. The config.log file comes > from the same folder libmesh_root, so how can it be inconsistent..? I don't know, but have no explanation for the appearance of the spurious strings "<http://c0.nc>" and "<http://c0_4.nc>" in the middle the output you sent, supposedly resulting from running the ncgen3/run_tests.sh and ncgen3/run_nc4_tests.sh shell scripts. Is it possible that the output you sent was accidentally modified when you cut and pasted it into the support request? When you run either of these ncgen3 scripts (after setting a srcdir environment variable to a path to the directory containing the ncgen3 sources), does the output you see still have "<http://c0"; strings in it? No other users have reported this problem, and the software passes all the tests on our test platforms, so I'm just guessing that the appearance of these spurious strings in the output of the failed tests has something to do with the cause of the test failures ... --Russ > On 5/28/14 6:38 PM, Unidata netCDF Support wrote: > > Bin, > > > > Something I didn't notice before may be the cause of the problem. > > > > It appears as if a test script in the netcdf-c sources has been > > changed, perhaps inadvertantly. Lines 7-8 of ncgen3/run_tests.sh > > should be: > > > > echo "*** creating classic file c0.nc from c0.cdl..." > > ./ncgen3 -b -o c0.nc $srcdir/c0.cdl > > > > but from the output you sent, it looks they have been changed to > > > > echo "*** creating classic file c0.nc <http://c0.nc> from c0.cdl..." > > ./ncgen3 -b -o c0.nc <http://c0.nc> $srcdir/c0.cdl > > > > and similarly for the test script ncgen3/run_nc4_tests.sh, which > > seems to have a similar change to > > > > echo "*** creating netCDF-4 file c0_4.nc <http://c0_4.nc> from c0.cdl..." > > ./ncgen3 -k3 -b -o c0_4.nc <http://c0_4.nc> $srcdir/c0.cdl > > > > We certainly don't have any occurrence of the string "<http://c0"; > > anywhere in the ncgen3 sources, so I can't reproduce the output and > > segmentation fault you are seeing. > > > > Can you check that those two testing scripts in your sources match what > > they should be here: > > > > https://github.com/Unidata/netcdf-c/blob/v4.3.1/ncgen3/run_tests.sh > > https://github.com/Unidata/netcdf-c/blob/v4.3.1/ncgen3/run_nc4_tests.sh > > > > If they match, the output you sent is inconsistent with what's in the > > scripts. > > > > If they don't match, perhaps some errant editing script modified the files > > ... > > > > --Russ > > > >> While compiling libMesh I got these failed tests related to netCFD. > >> Apparently they prevent me from using Exodus in libMesh. > >> > >> *** Testing ncgen3. > >> *** creating classic file c0.nc <http://c0.nc> from c0.cdl... > >> ../../../../../contrib/netcdf/v4/ncgen3/run_tests.sh: line 8: > >> 37560 Segmentation fault: 11 ./ncgen3 -b -o c0.nc > >> <http://c0.nc> $srcdir/c0.cdl > >> FAIL: run_tests.sh > >> *** Testing ncgen3 for netCDF-4. > >> *** creating netCDF-4 file c0_4.nc <http://c0_4.nc> from c0.cdl... > >> ../../../../../contrib/netcdf/v4/ncgen3/run_nc4_tests.sh: line > >> 8: 37581 Segmentation fault: 11 ./ncgen3 -k3 -b -o c0_4.nc > >> <http://c0_4.nc> $srcdir/c0.cdl > >> FAIL: run_nc4_tests.sh > >> ================================================ > >> 2 of 2 tests failed > >> Please report to address@hidden > >> <mailto:address@hidden> > >> ================================================ > >> > >> Can you see what is going wrong here? > >> > >> Thanks for helping, > >> Lorenzo > >> > >> -- > >> ============================ > >> Lorenzo Zanon, M.Sc. > >> Doctoral Candidate > >> > >> Graduate School AICES > >> RWTH Aachen University > >> SchinkelstraÃe 2 > >> 52062 Aachen > >> Deutschland > >> > >> address@hidden > >> +49 (0)241 80 99 147 > >> ============================ > >> > >> > >> > >> > >> > > Russ Rew UCAR Unidata Program > > address@hidden http://www.unidata.ucar.edu > > > > > > > > Ticket Details > > =================== > > Ticket ID: TEQ-670685 > > Department: Support netCDF > > Priority: Normal > > Status: Closed > > > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: TEQ-670685 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.