Dennis Heimbigner

I wasn't very clear about this. The question is: when you open using nc_open_mem, is it always read only?

I will check also. My speculation is that one of the URLs it is using is broken.

Ok, then the virtual driver we are using has probably changed on 1.12. I will investigate.

Looking at the cmake actions failure, I see this: > /home/runner/work/netcdf-c/netcdf-c/libhdf5/H5FDhttp.c:462:19: error: ‘H5FD_FEAT_DEFAULT_VFD_COMPATIBLE’ undeclared (first use in this function) Looks like something changed. I will see if I can run...

Weird. That macro is defined both in 1.10.7 and 1.12.0 in exactly the same .h file. Why is it not seeing it?

Don't remember about min version. I will test under linux on ubuntu 16.

So, I ran the test under unbuntu 16 with 1.12.0 with the 18 compatibility flag. It did not fail. Could this be a return of the bash vs sh issue?

This seems like an ok solution. For some other cases, we have modified the files being compared: tst_special_atts.cdl andref_tst_special_atts.cdl in this case. We edit the files to remove the endian...

```` < 0.589788025031098, 0.581683089463883, 0.573519986072457, --- > 0.589788025031098, 0.581683089463884, 0.573519986072457, ```` The problem is the middle value differs in the last digit: 3 vs 4. This occasionally occurs depending on...

If the data is being accesses with ncdump, then you might be able to use the -p flag.