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.

Sign up for GitHub

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

Jump to bottom

minc2-record-test segfaults with HDF5 1.12.0 #114

Closed
bcdarwin opened this issue Apr 15, 2021 · 4 comments
Closed

minc2-record-test segfaults with HDF5 1.12.0 #114

bcdarwin opened this issue Apr 15, 2021 · 4 comments

Comments

@bcdarwin
Copy link

Currently causing a libminc build failure in the Nixpkgs/NixOS CI (git bisect blames NixOS/nixpkgs@6696362):

Start 47: minc2-record-test
47/53 Test #47: minc2-record-test ................***Exception: SegFault  0.06 sec

Not yet sure if this indicates an underlying issue affecting the current MINC toolkit using 1.10.x for which the test passes or is due to an API channge.
@bcdarwin bcdarwin changed the title minc2-record-test segfaults with HDF 1.12.0 minc2-record-test segfaults with HDF5 1.12.0 Apr 15, 2021
@bcdarwin bcdarwin mentioned this issue Apr 15, 2021
Merged
8 tasks
bcdarwin added a commit to bcdarwin/nixpkgs that referenced this issue Apr 15, 2021
@bcdarwin
libminc: hdf5 -> hdf5_1_10
a7e6653 
- unbreaks build broken by merge of NixOS#117584/669636256265f6e47cc75126b7b003c4554d0acb
- needed due to libminc test segfault (BIC-MNI/libminc#114)
@seanm
Copy link
Contributor

seanm commented Jul 13, 2022

This test is passing for me with libminc (latest git) with hdf (latest git).

@gdevenyi
Copy link
Contributor

@bcdarwin I guess this means there was a bug in hdf5 that has been since resolved? Would be interesting to see if other sub-releases pass again

@vfonov
Copy link
Member

vfonov commented Jul 18, 2022

just FYI, there is no software that I am aware of that uses "record" data type that this test is testing.

@bcdarwin
Copy link
Author

It's passing for me as well with HDF5 1.12.1, although with segfaults or other memory corruption I never know what package to blame.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@seanm @bcdarwin @vfonov @gdevenyi