Hello, My apologies in the delayed response, I have been travelling. Disabling DAP tests is currently recommended, as these issues you're seeing are an issue with the remote server and not reflecting an issue in your build. If everything else passes, you should be fine. Thanks, I hope this helps, have a great day, -Ward > Some further information, when I use the ncdump command that is > created by the build, I get > > address@hidden dap4_test]$ ../ncdump/ncdump -h > '[dap4]http://remotetest.unidata.ucar.edu/d4ts/test.01' > /tmp/bennet/build/netcdf-c-4.7.3/ncdump/.libs/lt-ncdump: > [dap4]http://remotetest.unidata.ucar.edu/d4ts/test.01: > [dap4]http://remotetest.unidata.ucar.edu/d4ts/test.01: NetCDF: DAP > server error > > Looking at > https://remotetest.unidata.ucar.edu/d4ts/ > > I don't see test.01 listed, and when I examine > https://remotetest.unidata.ucar.edu/d4ts/test.01.xml > in the browser, then this URL generates an HTTP Status 500 message > > https://remotetest.unidata.ucar.edu/d4ts/test.01.xml.xml > > and these two return HTTP Status 404 messages > > https://remotetest.unidata.ucar.edu/d4ts/test.01.xml.dmr.xml > https://remotetest.unidata.ucar.edu/d4ts/test.01.xml.dap > > Perhaps that is useful? > > > > On Thu, Jan 30, 2020 at 6:23 PM Unidata netCDF Support > <address@hidden> wrote: > > > > > > Bennet Fauber, > > > > Thank you for contacting us. This is an automated response confirming the > > receipt of your ticket. One of our agents will get back to you as soon as > > possible. For your records, the details of the ticket are listed below. > > When replying, please make sure that the ticket ID is kept in the subject > > line to ensure that your replies are tracked appropriately. > > > > Ticket ID: TVE-757123 > > Subject: make check failure for test_remote.sh with Intel compilers > > 18.0.5 and 19.1 > > Department: Support netCDF > > Priority: Normal > > Status: Open > > > > > > > > The NetCDF libraries are developed at the Unidata Program Center, > > in Boulder, Colorado, funded primarily by the National Science Foundation . > > > > All support requests are handled by the development team. No dedicated > > support staff are funded at this time. For this reason we cannot guarantee > > response times, nor that we can resolve every support issue, although we > > do our best to respond within 72 hours. > > > > It is in the nature of support requests that the same question is asked many > > times. We urge you to search the support archives for material relating to > > your support request: > > > > http://www.unidata.ucar.edu/search.jsp?support&netcdf > > > > If you are having trouble building netCDF, please take a look at the > > "Building NetCDF" page: > > > > https://www.unidata.ucar.edu/software/netcdf/docs/getting_and_building_netcdf.html > > > > Windows users should see this paget: > > > > https://www.unidata.ucar.edu/software/netcdf/docs/winbin.html > > > > Complete documentation (including a tutorial, and sample programs in C, > > Fortran, > > Java, and other programming languages) can be found on the netCDF > > Documentation page: > > > > http://www.unidata.ucar.edu/software/netcdf/docs/ > > http://www.unidata.ucar.edu/software/netcdf/examples/programs/ > > > > If you resolve your issue through one of these methods, please send a reply > > to > > this email, letting us know that you no longer need support. This will help > > us spend more time on netCDF development. > > > > Best regards, > > > > Unidata User Support > > > > Ticket Details =================== Ticket ID: TVE-757123 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.
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.