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

Update UCX tests for new handshake step #4036

Merged
merged 2 commits into from
Aug 11, 2020

Conversation

jakirkham
Copy link
Member

@jakirkham jakirkham commented Aug 10, 2020

Follow-up to PR ( #4019 )

Recently Dask added a handshake step to communicate information like Python versions available and feature supported (compressors, out-of-band pickling, etc.). This causes some UCX test failures in their current form. So this updates them to fix that issue.

cc @quasiben @pentschev @madsbk @mrocklin

Recently Dask added a handshake step to communicate information like
Python versions available and feature supported (compressors,
out-of-band pickling, etc.). This causes some UCX test failures in their
current form. So this updates them to fix that issue.
@mrocklin
Copy link
Member

Thank you for this @jakirkham . This looks good to me. Will merge on passed tests.

Not sure why this test started segfaulting for me. However we have had some
history with segfault issues in these tests previously. So go ahead and just
disable this one with a note as to why.
Comment on lines +171 to +176
pytest.param(
lambda cudf: cudf.DataFrame({"a": ["a"]}).head(0),
marks=pytest.mark.skip(
reason="This test segfaults for some reason. So skip running it entirely."
),
),
Copy link
Member Author

@jakirkham jakirkham Aug 10, 2020

Choose a reason for hiding this comment

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

This started segfaulting for me. Not sure why. I don't think it is related to Distributed (maybe a cuDF issue?). For now am just disabling this test until we can figure out why/fix it.

Edit: Should add this has come up before ( #3279 ).

cc @kkraus14 @shwina (for vis)

Copy link
Member

Choose a reason for hiding this comment

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

Hmm this is news to me but is likely problematic. We'll have to poke around a little bit.

Copy link
Member Author

Choose a reason for hiding this comment

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

There is also another case in this test (shown below) that has been marked as failing for a while as well. Not sure if they are related.

pytest.param(
lambda cudf: cudf.DataFrame({"a": ["Check", "str"], "b": ["Sup", "port"]}),
marks=pytest.mark.skip(
reason="This test segfaults for some reason. So skip running it entirely."
),
),

Copy link
Member

Choose a reason for hiding this comment

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

I'm curious, did this fail before the recent handshake PR?

Copy link
Member Author

Choose a reason for hiding this comment

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

I haven't seen it in UCX-Py's CI, but did run into it locally. Maybe there's something more subtle at play like environment differences. In any event, I don't think it is handshake related.

@jakirkham jakirkham merged commit b5e72fc into dask:master Aug 11, 2020
@jakirkham jakirkham deleted the fix_ucx_tst_for_handshake branch August 11, 2020 01:33
@jakirkham
Copy link
Member Author

Merged to fix ucx-py CI. Hope that is ok 🙂

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.

3 participants