Skip to content

Conversation

@keewis
Copy link
Collaborator

@keewis keewis commented Jan 3, 2021

Some of the to_dask_dataframe tests fail on the upstream-dev CI because the behavior of pandas.DataFrame changed (see pandas-dev/pandas#38645). For now we can silence these by computing all dask arrays we pass to pandas.DataFrame.

@max-sixty
Copy link
Collaborator

Thanks @keewis

How should we think about changing the test code vs xfailing?

IIUC the current test code should work, but doesn't because of the pandas issue. Would we expect to revert this after pandas fixes its issue?

keewis and others added 2 commits January 3, 2021 22:39
Co-authored-by: Maximilian Roos <5635139+max-sixty@users.noreply.github.com>
@keewis
Copy link
Collaborator Author

keewis commented Jan 3, 2021

How should we think about changing the test code vs xfailing?

that's a good point. I'm really not sure: in this case we don't change the behavior of the test, but in general it would probably be better to xfail.

@dcherian
Copy link
Contributor

dcherian commented Jan 3, 2021

It's a bug in constructing an expected dataframe. Seems OK to change it and not revert once pandas fixes its behaviour.

Copy link
Collaborator

@max-sixty max-sixty left a comment

Choose a reason for hiding this comment

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

in this case we don't change the behavior of the test

I see, SGTM

@andersy005 andersy005 merged commit 8731acc into pydata:master Jan 4, 2021
@keewis keewis deleted the fix-dask-dataframe-tests branch January 4, 2021 15:23
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.

⚠️ Nightly upstream-dev CI failed ⚠️

4 participants