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.

Sign up for GitHub

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

Jump to bottom

Re-enable Support for Dask/Concurrent Futures Engines #3652

Closed
chukarsten opened this issue Aug 10, 2022 · 0 comments · Fixed by #3700
Closed

Re-enable Support for Dask/Concurrent Futures Engines #3652

chukarsten opened this issue Aug 10, 2022 · 0 comments · Fixed by #3700
Assignees
@jeremyliweishih

Comments

@chukarsten
Copy link
Contributor

chukarsten commented Aug 10, 2022 •
edited
Loading

The mentioned PR resulted in many Dask and concurrent futures related tests starting to flake. To keep up development, we marked many of the flaky tests with xfail. These tests need to have xfail removed and the underlying incompatibility with Woodwork 0.17.x, Dask and threading in general understood.

When these tests are enabled, it seems that something happens with the underlying block managers and there are size mismatches with pieces of the threaded arrays.

Originally posted by @jeremyliweishih in #3626 (comment)

Originally posted by @jeremyliweishih in #3626 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeremyliweishih jeremyliweishih

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Woodwork 0.18.0 compatibility alteryx/evalml
Remove xfails from compatibility alteryx/evalml
2 participants
@jeremyliweishih @chukarsten