-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Python][CI] AppVeyor CI is failing on test_fs.py::test_filesystem_is_functional_after_pickling #38431
Comments
The version of |
I think the failures are due to a arrow/python/pyarrow/tests/test_fs.py Lines 465 to 467 in 25e5d19
Will add a PR and see if this is it. |
Thanks for reporting @AlenkaF. I just ran into the same issue here while backporting a patch to PyArrow 13.0.0 on conda-forge: conda-forge/arrow-cpp-feedstock#1211 (comment) |
) ### Rationale for this change Appveyor CI is failing https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/48347810. It seems the reason for the test failures is a change in the `type_name` (from `"py::fsspec+s3"` to `"py::fsspec+('s3', 's3a')"`) and due to it tests are not being skipped. ### What changes are included in this PR? Update the check for `type_name` in case of `PyFileSystem(FSSpecHandler(s3fs.S3FileSystem()))`. * Closes: #38431 Authored-by: AlenkaF <frim.alenka@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
) ### Rationale for this change Appveyor CI is failing https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/48347810. It seems the reason for the test failures is a change in the `type_name` (from `"py::fsspec+s3"` to `"py::fsspec+('s3', 's3a')"`) and due to it tests are not being skipped. ### What changes are included in this PR? Update the check for `type_name` in case of `PyFileSystem(FSSpecHandler(s3fs.S3FileSystem()))`. * Closes: #38431 Authored-by: AlenkaF <frim.alenka@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
apache#38455) ### Rationale for this change Appveyor CI is failing https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/48347810. It seems the reason for the test failures is a change in the `type_name` (from `"py::fsspec+s3"` to `"py::fsspec+('s3', 's3a')"`) and due to it tests are not being skipped. ### What changes are included in this PR? Update the check for `type_name` in case of `PyFileSystem(FSSpecHandler(s3fs.S3FileSystem()))`. * Closes: apache#38431 Authored-by: AlenkaF <frim.alenka@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
apache#38455) ### Rationale for this change Appveyor CI is failing https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/48347810. It seems the reason for the test failures is a change in the `type_name` (from `"py::fsspec+s3"` to `"py::fsspec+('s3', 's3a')"`) and due to it tests are not being skipped. ### What changes are included in this PR? Update the check for `type_name` in case of `PyFileSystem(FSSpecHandler(s3fs.S3FileSystem()))`. * Closes: apache#38431 Authored-by: AlenkaF <frim.alenka@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Describe the bug, including details regarding any error messages, version, and platform.
As seen on a PR:
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/48347810
Currently our Appveyor CI seems to be failing on
python/pyarrow/tests/test_fs.py::test_filesystem_is_functional_after_pickling
with:Component(s)
Continuous Integration
The text was updated successfully, but these errors were encountered: