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

Add MGARD as a dependency to CI tests #1102

Closed
williamfgc opened this issue Jan 9, 2019 · 4 comments
Closed

Add MGARD as a dependency to CI tests #1102

williamfgc opened this issue Jan 9, 2019 · 4 comments
Assignees
Labels
status: wontfix This is either expected behavior or a known issue that wil not be addressed triage: low This issue is a nice-to-have if we can get to it but isn't holding anybody up.

Comments

@williamfgc
Copy link
Contributor

@chuckatkins I added some tests in #1101 that are only tested locally. I need your help to add to the CI build from the https://github.com/CODARcode/MGARD mgard3 branch. Thanks!

@williamfgc williamfgc changed the title Add MGARD to CI test Add MGARD as a dependency to CI tests Jan 9, 2019
@chuckatkins chuckatkins added the triage: low This issue is a nice-to-have if we can get to it but isn't holding anybody up. label Feb 15, 2019
@chuckatkins
Copy link
Contributor

Initial work revealed that MGARD internally causes segfaults on the CI images. Further testing revealed the problems are within MGard itself so we are unable to enable it in the ADIOS CI until it can cleanly run it's own test suite. Otherwise it will be a blocker for the rest of ADIOS CI.

@chuckatkins chuckatkins added status: wontfix This is either expected behavior or a known issue that wil not be addressed and removed help wanted labels Feb 15, 2019
@williamfgc
Copy link
Contributor Author

@tugluk please keep us posted. Thanks!

@chuckatkins
Copy link
Contributor

Closing for now. We can re-open when memory issues are addressed upstream.

@williamfgc
Copy link
Contributor Author

@chuckatkins thanks, MGARD is not providing a release or stable API, we should treat this as experimental.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: wontfix This is either expected behavior or a known issue that wil not be addressed triage: low This issue is a nice-to-have if we can get to it but isn't holding anybody up.
Projects
None yet
Development

No branches or pull requests

2 participants