-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Dataset] Exclude breaking test case in read_parquet_benchmark_single_node
release test
#31904
[Dataset] Exclude breaking test case in read_parquet_benchmark_single_node
release test
#31904
Conversation
Signed-off-by: Scott Lee <sjl@anyscale.com>
should this be added as a |
Can we get a review of this? This is a release blocker. cc @clarkzinzow @c21 @amogkam @jianoaix |
@scottjlee can you try running this manually (i.e. fire off a release test before merging) to confirm that it fixes the issue? |
If this is a problem that users will run into, then we should update setup.py and add pickle5 as a dependency for the ray[data] install with python<=3.7 instead of just adding it to the app config |
Yeah, looks like the test actually exposed a prod issue for users that we need to fix. |
Signed-off-by: Scott Lee <sjl@anyscale.com>
I'm waiting on getting access to AWS roles/credentials to run release tests locally. Is there another way to kickoff release tests without merging? @cadedaniel In the meantime, @amogkam -- are the changes I made in |
Signed-off-by: Scott Lee <sjl@anyscale.com>
Signed-off-by: Scott Lee <sjl@anyscale.com>
Signed-off-by: Scott Lee <sjl@anyscale.com>
Signed-off-by: Scott Lee <sjl@anyscale.com>
pickle5
to Dataset app_config.yaml
to fix Data release test on Python 3.7pickle5
to dependencies for Python < 3.7 to fix release tests
Looks like the failing release test passes now: https://buildkite.com/ray-project/release-tests-pr/builds/26524 |
python/setup.py
Outdated
|
||
data_extras = [numpy_dep, pandas_dep, pyarrow_dep, "fsspec"] | ||
# Need pickle5 package to override default pickle package for Python < 3.7 | ||
if sys.version_info < (3, 7): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah this should be < (3, 8)
right?
if sys.version_info < (3, 7): | |
if sys.version_info < (3, 8): |
We ran the failing release test on a cluster with the same environment (notably Python 3.7), and determined that the failure is contained to the portion which tests a Dataset with a filter expression (the error is related to pickling with this filter expression). Therefore, we will temporarily disable this portion of the test, while keeping the rest of the release test (which I verified passes on the same cluster). We can come back to this in the future and fix the case with filter, but should not be a release blocker now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @scottjlee!
Once the release test run passes, this should be good to merge! |
Thanks @scottjlee! can we update the title and the pr description as well |
pickle5
to dependencies for Python < 3.7 to fix release testsread_parquet_benchmark_single_node
release test
Signed-off-by: Scott Lee <sjl@anyscale.com>
Signed-off-by: Scott Lee <sjl@anyscale.com>
Signed-off-by: Scott Lee <sjl@anyscale.com>
…e_node` release test (ray-project#31904) The release test read_parquet_benchmark_single_node fails, due to using Python 3.7 and not having the pickle5 package installed. A similar issue is discussed in ray-project#26225. We found that the test failure is contained to the portion which tests a Dataset with a filter expression (the error is related to pickling with this filter expression). Therefore, we will temporarily disable this portion of the test, while keeping the rest of the release test (which I verified passes on the same cluster). We can come back to this in the future and fix the case with filter. Example of release test successfully running with the filter case removed. Signed-off-by: Scott Lee <sjl@anyscale.com> Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Signed-off-by: Scott Lee sjl@anyscale.com
Why are these changes needed?
The release test
read_parquet_benchmark_single_node
fails, due to using Python 3.7 and not having thepickle5
package installed. A similar issue is discussed in #26225. We found that the test failure is contained to the portion which tests a Dataset with a filter expression (the error is related to pickling with this filter expression).Therefore, we will temporarily disable this portion of the test, while keeping the rest of the release test (which I verified passes on the same cluster). We can come back to this in the future and fix the case with filter. Example of release test successfully running with the filter case removed.
Related issue number
Closes #31888
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.