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

HDF5 crash for allGroupPath failure to append in the attribute #925

Closed
10 tasks done
alfoa opened this issue Feb 27, 2019 · 2 comments · Fixed by #926
Closed
10 tasks done

HDF5 crash for allGroupPath failure to append in the attribute #925

alfoa opened this issue Feb 27, 2019 · 2 comments · Fixed by #926
Assignees
Labels
defect devel issues in current devel priority_normal

Comments

@alfoa
Copy link
Collaborator

alfoa commented Feb 27, 2019


Issue Description

A user reported the following issue with the HDF5

Hi to all,

I am trying to create a database with 1024 histories but the process crash with:

RuntimeError: Unable to create attribute (object header message is too large)

The database is generated but it contain 951 histories only. Do you have any suggestion?

The RAVEN version I am using is compiled from the default branch of the 10/28/18.

Please find attached the tail of the raven output log file.

Best Regards,

Paolo
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@alfoa alfoa self-assigned this Feb 27, 2019
@alfoa alfoa added priority_normal defect devel issues in current devel labels Feb 27, 2019
@alfoa
Copy link
Collaborator Author

alfoa commented Feb 27, 2019

No wrong results for the users but just a crash

alfoa added a commit that referenced this issue Feb 27, 2019
@alfoa alfoa mentioned this issue Feb 27, 2019
8 tasks
@mandd mandd closed this as completed in #926 Mar 3, 2019
mandd added a commit that referenced this issue Mar 3, 2019
@mandd
Copy link
Collaborator

mandd commented Mar 3, 2019

issue closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect devel issues in current devel priority_normal
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants