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
New valgrind warnings after upgrade to NeXus 3.3 on RHEL #11759
Labels
Framework
Issues and pull requests related to components in the Framework
Milestone
Comments
This issue was originally trac ticket 10920 |
martyngigg
added
the
Framework
Issues and pull requests related to components in the Framework
label
Jun 3, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
DanNixon
added a commit
that referenced
this issue
Jun 4, 2015
Conflicts: Code/Mantid/Framework/PythonInterface/plugins/algorithms/WorkflowAlgorithms/IndirectCalibration.py Refs #11759
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
APITest has picked up some valgrind errors that originate in NeXus when moving to v4.3.3 on RHEL.
We need a new suppression to cover this:
The text was updated successfully, but these errors were encountered: