-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another round of Coverity cleanups, (minor) speedups, bug-fixes and test updates. #14
Conversation
…ed and an error occurs after an "exit:" label. Corrected a dozen Coverity errors (mainly allocation issues, along with a few other things): 711711, 711802, 711803, 711905, 970825, 996123, 996124, 1025787, 1047274, 1130013, 1130014, 1139538 Refactored internal fill-value code to correctly handle string types, and especially to allow NULL pointers and null strings (ie. "") to be distinguished. The code now avoids partially aliasing the two together (which only happened on the 'write' side of things and wasn't reflected on the 'read' side, adding to the previous confusion). Probably still weak on handling fill-values of variable-length and compound datatypes. Refactored the recursive metadata reads a bit more, to process HDF5 named datatypes and datasets immediately, avoiding chewing up memory for those types of objects, etc. Finished uncommenting and updating the nc_test4/tst_fills2.c code (as I'm proceeding alphabetically through the nc_test4 code files).
Seeing a failure in
I've poked around a bit, but since For completeness sake, I've tested this on an OSX and 32-bit Linux machine. NetCDF was built as follows:
Information regarding this failure may be found on the netCDF CDash Dashboard: http://my.cdash.org/testSummary.php?project=644&name=nc_test4_tst_strings&date=2013-12-30 I'm not sure about the proper workflow; whether to close this pull request, or if it can be updated in-place. -Ward |
Hi Ward,
On Dec 30, 2013, at 4:57 PM, Ward Fisher [email protected] wrote:
|
Hi Ward,
On Dec 30, 2013, at 4:57 PM, Ward Fisher [email protected] wrote:
|
Hi Quincey, No problem. If you are interested, our CDash dashboard is publicly available: http://my.cdash.org/index.php?project=netcdf-c When configuring/building with cmake, you can use the If you aren't registered, I'll set up an account for you using the email address that you're using for the rest of the contract work. My workflow typically goes like this, just for reference:
The nice thing with this type of testing is that tests aren't just evaluated on whether they passed or failed, but if the time it took to run was more than 2 standard deviations from the 'normal' test time. If so, it flags a timing failure to let you know that the test passed, but ran much more slowly than usual. |
correctly for variables with string datatype, plus a few other minor changes.
Conflicts: libdap2/common34.c oc2/ocutil.c
I've added some more commits to this (I think). Are they added to my previous changes, or do I need to use a separate pull request? Here's my changelog for the most recent set of commits: h5_test/tst_h_vars2.c: include/nc4internal.h: include/nc_logging.h: include/ncdispatch.h: libdap2/common34.c: libdap2/ncdap3.c: libdispatch/dfile.c: libsrc/ncx.c: libsrc/ncx.m4: libsrc/putget.c: libsrc4/Makefile.am: libsrc4/nc4attr.c: libsrc4/nc4dim.c: libsrc4/nc4file.c: libsrc4/nc4hdf.c: libsrc4/nc4internal.c: libsrc4/nc4type.c: libsrc4/nc4var.c: libsrc4/ncfunc.c: nc_test4/tst_fills2.c: nc_test4/tst_strings.c: ncdump/cdl4/ref_typescope.cdl: ncdump/nccopy.c: ncdump/ncdump.c: ncdump/utils.c: ncdump/utils.h: ncgen/ncgen.l: ncgen/ncgen.y: ncgen3/c0.cdl: oc2/ocutil.c: |
On 2/12/14, 7:53 AM, Quincey Koziol wrote:
I wasn't sure of this, but asking the git guru's at lunch, it seems like -Ward
|
Hi Ward, On Feb 12, 2014, at 1:28 PM, Ward Fisher [email protected] wrote:
|
…h_dispatch move hdf4 to its own dispatch layer
Corrected "BAIL" macros to avoid infinite loop when logging is disabled and an
error occurs after an "exit:" label.
Corrected a dozen Coverity errors (mainly allocation issues, along with a few
other things):
711711, 711802, 711803, 711905, 970825, 996123, 996124, 1025787,
1047274, 1130013, 1130014, 1139538
Refactored internal fill-value code to correctly handle string types, and
especially to allow NULL pointers and null strings (ie. "") to be
distinguished. The code now avoids partially aliasing the two together
(which only happened on the 'write' side of things and wasn't reflected on
the 'read' side, adding to the previous confusion).
Refactored the recursive metadata reads a bit more, to process HDF5 named
datatypes and datasets immediately, avoiding chewing up memory for those
types of objects, etc.
Finished uncommenting and updating the nc_test4/tst_fills2.c code (as I'm
proceeding alphabetically through the nc_test4 code files).