Hi,
A minor note on the binary verification. The wheel verification job
for Almalinux 8 has been timing out consistently, see [1].
After some investigation I've realised there's a specific test
(test_s3_options) that takes a long time probably due to S3
credentials resolution timeout. The test has always taken a long time
to finish but a specific commit on the release [2] doubles the test
cases performed around it. The test takes now ~11 minutes to complete
on this specific scenario and given we test for several Python
versions the 30 minutes timeout for the job isn't enough.
I've validated locally that the verification is successful, given
enough time. I've also validated locally that skipping the
aforementioned test makes the verification successful in a
"reasonable" amount of time.
If someone wants to validate you can apply the following patch:
diff --git a/ci/scripts/python_wheel_unix_test.sh
b/ci/scripts/python_wheel_unix_test.sh
index 2b8ee7be74..b55b07401f 100755
--- a/ci/scripts/python_wheel_unix_test.sh
+++ b/ci/scripts/python_wheel_unix_test.sh
@@ -116,5 +116,5 @@ if [ "${CHECK_UNITTESTS}" == "ON" ]; then
# Execute unittest, test dependencies must be installed
python -c 'import pyarrow; pyarrow.create_library_symlinks()'
- python -m pytest -r s --pyargs pyarrow
+ python -m pytest -r s --pyargs pyarrow -k "not test_s3_options"
fi
And test as we do in CI with docker and archery:
ALMALINUX=8 archery docker run -e TEST_DEFAULT=0 -e TEST_WHEELS=1 -e
VERBOSE=1 -e VERIFY_RC=0 -e VERIFY_VERSION=24.0.0 -e
GH_TOKEN=$GH_TOKEN almalinux-verify-rc
Given that the test is successful given enough time and that it can be
easily verified locally I don't think this is a blocker.
I've created an issue [3] to reduce the required time for this test to pass.
Regards,
Raúl
[1]
https://github.com/apache/arrow/actions/runs/24404382517/job/71425229713?pr=49742
[2]
https://github.com/apache/arrow/commit/0124d5b5b7f60b6ae6312bbb962dcff6dd4bc641
[3] https://github.com/apache/arrow/issues/49757
El mié, 15 abr 2026 a las 11:36, Raúl Cumplido (<[email protected]>) escribió:
>
> Hi,
>
> I would like to propose the following release candidate (RC0) of Apache
> Arrow version 24.0.0. This is a release consisting of 258
> resolved GitHub issues[1].
>
> This release candidate is based on commit:
> 31b4b6c0a0a7e7c117312d285541a21446675ec6 [2]
>
> The source release rc0 is hosted at [3].
> The binary artifacts are hosted at [4][5][6][7][8][9].
> The changelog is located at [10].
>
> Please download, verify checksums and signatures, run the unit tests,
> and vote on the release. See [11] for the SHA-512 checksum for this RC and
> [12]
> for how to validate a release candidate.
>
> See also a verification result on GitHub pull request [13].
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Release this as Apache Arrow 24.0.0
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow 24.0.0 because...
>
> [1]:
> https://github.com/apache/arrow/issues?q=is%3Aissue+milestone%3A24.0.0+is%3Aclosed
> [2]:
> https://github.com/apache/arrow/tree/31b4b6c0a0a7e7c117312d285541a21446675ec6
> [3]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-24.0.0-rc0
> [4]: https://packages.apache.org/artifactory/arrow/almalinux-rc/
> [5]: https://packages.apache.org/artifactory/arrow/amazon-linux-rc/
> [6]: https://packages.apache.org/artifactory/arrow/centos-rc/
> [7]: https://packages.apache.org/artifactory/arrow/debian-rc/
> [8]: https://packages.apache.org/artifactory/arrow/ubuntu-rc/
> [9]: https://github.com/apache/arrow/releases/tag/apache-arrow-24.0.0-rc0
> [10]:
> https://github.com/apache/arrow/blob/31b4b6c0a0a7e7c117312d285541a21446675ec6/CHANGELOG.md
> [11]:
> ffbac0c198c74f26b2ac173aa2b054cfd3902927ca3db36fbbae25353e8696c32b744e805c25801ced22641af71a5a8ea441202d8d3494aa803b797995d9d408
> [12]: https://arrow.apache.org/docs/developers/release_verification.html
> [13]: https://github.com/apache/arrow/pull/49742
