Skip to content

Fix the test suite on dask 0.15.3 #1610

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

Merged
merged 5 commits into from
Oct 5, 2017
Merged

Conversation

shoyer
Copy link
Member

@shoyer shoyer commented Oct 4, 2017

Our test suite is currently failing due to dask/dask#2718. This marks the failure as expected, which will make our CI a reliable indicator again.

Copy link
Member

@jhamman jhamman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shoyer - looks like we have one more dask test failing. Otherwise, looks good to me.

@shoyer shoyer force-pushed the fix-tests-dask0.15.3 branch from e46753d to bd3eb96 Compare October 5, 2017 15:17
@@ -473,7 +476,6 @@ def test_from_dask_variable(self):
self.assertLazyAndIdentical(self.lazy_array, a)


@requires_dask
@pytest.mark.parametrize("method", ['load', 'compute'])
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jhamman For future reference, it looks like pytest.mark.parametrize doesn't play well with the unittest based skiptest decorator. So I switched the import check to use something different for this module, but it's something we'll have to watch out for in the future, too.

@shoyer shoyer merged commit 30160ba into pydata:master Oct 5, 2017
@shoyer shoyer deleted the fix-tests-dask0.15.3 branch October 6, 2017 02:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants