[Bug]: Failures in HDF5Write_test
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3
- Forks
- 5
- Avg merge
- 4h 42m
- Merged PRs (30d)
- 6
Description
Description
The HDF5Write_test unit test is currently failing with segmentation violations:
2026-Jun-25 11:53:43,106 ERROR [static void ers::ErrorHandler::SignalHandler::action(int, siginfo_t*, void*) at /tmp/root/spack-stage/spack-stage-ers-NB_DEV_260625_A9-qimn5nong7ycomi2ldzkm47tzf2slyky/spack-src/src/ErrorHandler.cpp:101] Got signal 11 Segmentation fault (invalid memory reference)
Parameters = 'name=Segmentation fault (invalid memory reference)' 'signum=11'
Qualifiers = 'unknown'
host = daq.fnal.gov
user = amogan (52279)
process id = 4073458
thread id = 4073458
Steps to reproduce
In a fresh shell on daq.fnal.gov,
source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh
setup_dbt latest
dbt-create -n last_fddaq dev
cd dev && source env.sh
cd sourcecode
git clone https://github.com/DUNE-DAQ/dfmodules
dbt-build --unittest dfmodules
Version and environment
This appears to be only from the latest nightly. This did not happen during the nightly unit tests two days ago.
$ dbt-info release
Release type: fddaq
Release name: NFD_DEV_260625_A9
Base release name: NB_DEV_260625_A9
Release dir: /cvmfs/dunedaq-development.opensciencegrid.org/nightly/NFD_DEV_260625_A9
Impact
Small/Isolated
Anything else?
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce HDF5Write_test from a fresh shell on daq.fnal.gov using the listed setup_dunedaq, setup_dbt, dbt-create, clone, and dbt-build commands. Begin by confirming the failure in the NFD_DEV_260625_A9 nightly environment; done means the unit test no longer segfaults and the dfmodules unit-test build completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100