Skip to content

Conversation

@bgrant
Copy link
Contributor

@bgrant bgrant commented Aug 11, 2014

Here I add a function import_parallel_h5py to testing.py that tries to import a parallel-enabled h5py, and if one isn't available, it raises unittest.SkipTest. This replaces most of our uses of import_or_skip (but not all) and calls import_or_skip under the hood.

Unfortunately, @kwmsmith, it seems to make our paralleltests hang in my testing environment that actually has a parallel build of h5py. It skips tests correctly when there is no h5py or when there is a serial h5py installed.

Not ready for merge.

bgrant added 3 commits August 11, 2014 15:31
It skips if h5py isn't available OR if it is available but doesn't support parallel operations.
@bgrant bgrant added easy and removed easy labels Aug 11, 2014
@bgrant bgrant added this to the 0.6 milestone Aug 11, 2014
@bgrant
Copy link
Contributor Author

bgrant commented Aug 11, 2014

Hm. It seems to reliably hang on Travis.

@kwmsmith
Copy link
Contributor

Looks like it's hanging at the parallel test part -- any idea why?

@bgrant
Copy link
Contributor Author

bgrant commented Oct 16, 2015

Moving to 0.7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants