zanmato1984 opened a new issue, #49768:
URL: https://github.com/apache/arrow/issues/49768
While verifying the Apache Arrow 24.0.0 RC0 source release on macOS arm64,
the C++ release verification fails reproducibly in `parquet-encryption-test`.
I first hit an unrelated local `ccache` issue, but after disabling `ccache`
the C++ verification still fails in the same place, so this appears to be a
real RC / test-data problem rather than a local toolchain problem.
I reproduced this with:
```bash
ARROW_USE_CCACHE=OFF TEST_DEFAULT=0 TEST_CPP=1 TEST_PYTHON=0
./verify-release-candidate.sh 24.0.0 0
```
I also saw the same failure when running the original mixed verification
command after isolating the local `ccache` problem.
`ctest` reports 1 failure out of 104 tests:
```text
117 - parquet-encryption-test (Failed)
```
The failing test is:
```text
EncryptedBloomFilterReader.ReadEncryptedBloomFilter
```
The failure is:
```text
C++ exception with description "IOError: Failed to open local file
'.../cpp/submodules/parquet-testing/data/encrypt_columns_and_footer_bloom_filter.parquet.encrypted'.
Detail: [errno 2] No such file or directory" thrown in the test body.
```
The referenced test is in:
```text
cpp/src/parquet/encryption/bloom_filter_encryption_test.cc
```
and it expects this fixture:
```text
encrypt_columns_and_footer_bloom_filter.parquet.encrypted
```
In the prepared RC verification tree, that file was not present under:
```text
cpp/submodules/parquet-testing/data/
```
At the end of the run:
```text
99% tests passed, 1 tests failed out of 104
The following tests FAILED:
117 - parquet-encryption-test (Failed)
```
Expected behavior:
the 24.0.0 RC0 C++ release verification should pass, or this test should not
depend on a fixture that is missing from the prepared release verification data.
Environment:
- OS: macOS arm64
- Compiler: AppleClang 21.0.0.21000099
- CMake: 4.0.3
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
