-
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
GH-38431: [Python][CI] Update fs.type_name checks for s3fs tests #38455
Conversation
AppVeyor is passing but other Python builds are still using the old version of |
@github-actions crossbow submit -g python |
Revision: 3a53d11 Submitted crossbow builds: ursacomputing/crossbow @ actions-a83bce7a72 |
@github-actions crossbow submit -g conda |
Revision: 3a53d11 Submitted crossbow builds: ursacomputing/crossbow @ actions-716f9fca2a |
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.
+1
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 3f4aeab. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 5 possible false positives for unstable benchmarks that are known to sometimes produce them. |
) ### 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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
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 ofPyFileSystem(FSSpecHandler(s3fs.S3FileSystem()))
.