mirror of
https://github.com/Unidata/netcdf-c.git
synced 2024-11-27 07:30:33 +08:00
7223c4a5aa
re: https://github.com/Unidata/netcdf-c/issues/1451 The situation with the various DAP (and other) remote test servers is currently in a state of flux. For example, Unidata admin is planning to forcibly shift the remote test server to remotetest.unidata.ucar.edu soon. In addition, the server test.opendap.org has shown some recent instability. The result is that various DAP (and byterange) tests can fail unexpectedly. This is an irritant to users and reveals nothing about test sucess or failure. Solve by modifying tests to report server inaccessibility and otherwise pretend to succeed. This puts an onus on Unidata to detect such server failures, but will not cause users to see spurious failures. [Note. Do similar fix for netcdf-java]. The check is: 1. export SETX=1 to cause all the shell scripts to trace 2. search the log files for the phrase "WARNING" (in upper case) and see if it is complaining about not finding a server. Misc. Changes ------------- 1. Added a pingurl program to see if a server was up. 2. modified some test case url targets |
||
|---|---|---|
| .. | ||
| baseline | ||
| baselineraw | ||
| baselineremote | ||
| cdltestfiles | ||
| daptestfiles | ||
| dmrtestfiles | ||
| misctestfiles | ||
| nctestfiles | ||
| CMakeLists.txt | ||
| d4test_common.sh | ||
| Makefile.am | ||
| maketests.sh | ||
| test_common.h | ||
| test_data.c | ||
| test_data.sh | ||
| test_environment4.c | ||
| test_fillmismatch.sh | ||
| test_hyrax.sh | ||
| test_meta.c | ||
| test_meta.sh | ||
| test_parse.c | ||
| test_parse.sh | ||
| test_raw.sh | ||
| test_remote.sh | ||
| test_test.sh | ||
| tst_curlopt.sh | ||
| tst_data.sh | ||
| tst_meta.sh | ||
| tst_parse.sh | ||
| tst_raw.sh | ||