Thanks for the interesting discussion.
Regarding the maintenance work, that's a good point. I now have
the capacity to maintain Arrow C++ and Java again, which wasn’t
possible for the past few years. However, I’m not entirely sure
if I’ll be able to work on enabling more components. Hopefully,
som
Thanks Antoine, that's a good point. Maybe we should prioritise the
definition of our support policy [1] before adding new platforms, build
systems, etcetera.
[1] https://github.com/apache/arrow/issues/46002
El lun, 12 may 2025 a las 10:52, Antoine Pitrou ()
escribió:
>
> Hello,
>
> I'm sure the
Hello,
I'm sure the technical details can be ironed out, but the question is
more whether someone is willing to do the maintenance work required to
keep Arrow working on big-endian platforms, and if possible enable it
for more components (most of us don't have access to such a platform).
If
Hi,
Thanks for pushing this, adding s390x to our testing matrix sounds
interesting to me. We have had discussions in the past about ephemeral
runners [1] and the potential security risks. In that issue there was a
discussion about how the pytorch project sets those "ephemeral" runners,
see their w
Hi,
CI for s390x on Apache Arrow has not been enabled since we previously
relied on the unstable Travis environment.
Now, IBM offers permanent virtual instances for open source projects
[1]. I’m considering using these instances for s390x CI as a
self-hosted runner for GitHub Actions. I’ve alread
