[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #ZSJ-783149]: Question about building netCDF libs on RHEL4

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.

  • Subject: [netCDF #ZSJ-783149]: Question about building netCDF libs on RHEL4
  • Date: Sun, 28 Jan 2007 15:34:08 -0700
Trevor,

No, "make check" will not stop if an error is encountered, but instead 
completes as many tests as possible.  However, every error message emitted 
includes the word "FAILURE" in all caps, so if you grep for that in the output 
and don't find it, you can be sure there were no problems.  As an example, 
here's what the output from a test failure looks like:

 ...
*** Testing nc_put_att_short ...  15 good comparisons. ok
*** Testing nc_put_att_int ...  19 good comparisons. ok
*** Testing nc_put_att_long ... 
        FAILURE at line 7211 of test_put.c: range error: status = 0
        FAILURE at line 7211 of test_put.c: range error: status = 0
        FAILURE at line 1254 of test_put.c: att value read not that expected
 18 good comparisons. 
        ### 3 FAILURES TESTING nc_put_att_long! ###
*** Testing nc_put_att_float ...  21 good comparisons. ok
*** Testing nc_put_att_double ...  27 good comparisons. ok
 ...

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: ZSJ-783149
Department: Support netCDF
Priority: Normal
Status: Closed