Skip to content
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

Fix for Github issue netcdf-c 300 #301

Merged
merged 7 commits into from
Aug 17, 2016
Merged

Fix for Github issue netcdf-c 300 #301

merged 7 commits into from
Aug 17, 2016

Conversation

DennisHeimbigner
Copy link
Collaborator

Modified provenance code to allocate the minimal space
needed for _NCProperties attribute in file. Basically
required using malloc in the provenance code and in ncdump.
Now an empty file is about 66 bytes larger than pre-provenance.
Otherwise should cause no externally visible effects.
Also removed the ENABLE_FILEINFO from configure.ac since
the provenance code is no longer optional.

Modified provenance code to allocate the minimal space
needed for _NCProperties attribute in file.  Basically
required using malloc in the provenance code and in ncdump.
Otherwise should cause no externally visible effects.
Also removed the ENABLE_FILEINFO from configure.ac since
the provenance code is no longer optional.
@WardF
Copy link
Member

WardF commented Aug 8, 2016

The non-serial tests are failing but I don't know why yet; looking into it and will report what I find between other meetings today.

@WardF
Copy link
Member

WardF commented Aug 8, 2016

My mistake. It's not parallel images failing, it appears to be ones which run without netcdf-4 enabled, so it's probably just some option/code/include fenceposting that's needed.

@DennisHeimbigner
Copy link
Collaborator Author

When I run by hand with netcdf-4 turned off, it works, both with automake and cmake.
Is there any way to get travis to output more info, I can turn on some debug output flags,
but travis swallows it up.

@WardF
Copy link
Member

WardF commented Aug 9, 2016

It's possible to open the raw log from travis; when you go in to view the build log, at the top of the output panel on the right there is a button that says 'Raw log'.

The issue is with 32-bit systems. In `ncdump/tst_ncgen4.sh', the following is shoping up when testing special attributes:


*** Testing: ref_tst_special_atts3
*** SUCCEED: ref_tst_special_atts3
*** Testing: ref_tst_special_atts
47c47
<       :_NCProperties = "version=1|netcdflibversion=4.4.2-development|hdf5libversion=1.8.17� I" ;
---
>       :_NCProperties = "version=1|netcdflibversion=4.4.2-development|hdf5libversion=1.8.17I" ;
*** FAIL: ref_tst_special_atts

@DennisHeimbigner
Copy link
Collaborator Author

Ok, the string is not being null terminated. I will recheck my code.
=Dennis

On 8/8/2016 6:29 PM, Ward Fisher wrote:

It's possible to open the raw log from travis; when you go in to view
the build log, at the top of the output panel on the right there is a
button that says 'Raw log'.

The issue is with 32-bit systems. In `ncdump/tst_ncgen4.sh', the
following is shoping up when testing special attributes:

|*** Testing: ref_tst_special_atts3 *** SUCCEED: ref_tst_special_atts3
*** Testing: ref_tst_special_atts 47c47 < :_NCProperties =
"version=1|netcdflibversion=4.4.2-development|hdf5libversion=1.8.17� I"
; --- > :_NCProperties =
"version=1|netcdflibversion=4.4.2-development|hdf5libversion=1.8.17I" ;
*** FAIL: ref_tst_special_atts |


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#301 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3P2wwZzO3jewhTAXAuxRJJigurGgufks5qd8nbgaJpZM4JfKPu.

@WardF
Copy link
Member

WardF commented Aug 9, 2016

Super thanks Dennis! I'll get these merged ASAP.

@WardF WardF merged commit f629bba into master Aug 17, 2016
@DennisHeimbigner DennisHeimbigner deleted the gh300.dmh branch August 17, 2016 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants