Open mgorny opened 8 months ago
The first error looks like we need to use the platform specific int type instead of int64 (haven't looked too closely, though).
The rest seem like they could potentially be related to bugs in Arrow.
I already have a fix for one bug in Arrow, so I'm going to retry with it applied, later today.
Yeah, my patch fixed pandas/tests/interchange/test_impl.py::test_large_string_pyarrow
. I'll check if I can figure out a fix for the other three when I find some time.
Pandas version checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pandas.
[ ] I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
When running the test suite on 32-bit x86 with
pyarrow
installed, I'm getting the following test failures (compared to a run withoutpyarrow
):Tracebacks
```pytb _______________________________________ TestGetIndexer.test_get_indexer_arrow_dictionary_target _______________________________________ [gw8] linux -- Python 3.11.7 /var/tmp/portage/dev-python/pandas-2.2.0-r1/work/pandas-2.2.0-python3_11/install/usr/bin/python3.11 self =Full build & test log (2.5M .gz, 52M uncompressed): pandas.txt.gz
This is on Gentoo/x86 systemd-nspawn container. I'm using
-O2 -march=pentium-m -mfpmath=sse -pipe
flags to rule out i387-specific precision issues.I've also filed https://github.com/apache/arrow/issues/40153 for test failures in pyarrow itself. Some of them could be possibly be bugs in pandas instead.
Expected Behavior
Tests passing ;-).
Installed Versions