GH-44095: [CI][Python] Enable S3 testing on Windows wheel builds

[pitrou]

Rationale for this change

We currently build Windows wheels with S3 enabled, but we disable it for testing.

What changes are included in this PR?

Ensure Minio is installed and re-enable S3 for testing.

Are these changes tested?

Yes, by construction (on CI).

Are there any user-facing changes?

No.

• GitHub Issue: [Python][CI] Enable S3 tests on Windows wheel builds #44095

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview

[pitrou]

@github-actions crossbow submit wheelwin*

[github-actions]

⚠️ GitHub issue #44095 has been automatically assigned in GitHub to PR creator.

[pitrou]

@github-actions crossbow submit wheel-windows-*

[github-actions]

Revision: 7ee9186

Submitted crossbow builds: ursacomputing/crossbow @ actions-7c69e5dac0

Task	Status
wheel-windows-cp310-amd64
wheel-windows-cp311-amd64
wheel-windows-cp312-amd64
wheel-windows-cp313-amd64
wheel-windows-cp38-amd64
wheel-windows-cp39-amd64

[kou]

Hmm. It seems that s3fs isn't built...

https://github.com/ursacomputing/crossbow/actions/runs/10836975764/job/30071907274#step:9:951

SKIPPED [1] Python312\Lib\site-packages\pyarrow\tests\test_fs.py:607: could not import 's3fs': No module named 's3fs'

[kou]

Ah, it's not pyarrow._s3fs.

[kou]

+1

[pitrou]

Ah, it's not pyarrow._s3fs.

Yes, it's always confusing :) The error message is talking about https://pypi.org/project/s3fs/.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 0 benchmarking runs that have been run so far on merge-commit a828bd2.

None of the specified runs were found on the Conbench server.

The full Conbench report has more details.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit a828bd2.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 35 possible false positives for unstable benchmarks that are known to sometimes produce them.