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

960531: netCDF fortran test ok?

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: 960531: netCDF fortran test ok?
  • Date: Fri, 31 May 96 16:17:53 -0600
Neil,

> To: address@hidden
> From: "Neil R. Smith" <address@hidden>
> >Subject: netCDF fortran test ok?
> >Organization: Dept. Meteorology/Texas A&M University
> >Keywords: 199605311846.AA15072

In the above message you wrote:

> I configure, make, make test.  On the fortran tests I get
> ...
> *** Testing nccre ...
> *** Testing ncddef ...
> *** Testing ncvdef ...
> ...
> with no "ok" as I got on the nctest dir, e.g.,
> ...
> *** Testing nccreate ...        ok ***
> *** Testing ncopen ...          ok ***
> *** Testing ncredef ...         ok ***
> ...
> No errors are otherwise present in the make test output.
> 
> Is there something wrong indicated here with this fortran test?

There's nothing wrong, we just didn't insert the `ok ***' suffix on the
print line.  If something goes wrong, the package *will* let you know.

You raise a good point, though.  I'll see about making the printout more
consistent.

--------
Steve Emmerson   <address@hidden>