The only experience I have with the s390x jobs is that a while back when I had merged in some changes for Go's Parquet build that broke the s390x build there was a user who submitted an issue about the crash and failing test on s390x. So I know there's at least one user who was actively using it on s390x via Go at that time.
That said, I otherwise agree with you that I think the primary use of the job is ensuring all the tests work on a big-endian architecture and (IMO) we shouldn't abandon that. On Thu, Apr 20, 2023 at 4:30 PM Dewey Dunnington <de...@voltrondata.com.invalid> wrote: > I wonder if the main use of the s390x job is to ensure that Arrow > works on big endian? If there are any claims about working with/on big > endian in the code base (e.g., the existence of a > ARROW_IS_LITTLE_ENDIAN macro) I think it's essential that it is tested > somewhere. Deciding to abandon big endian is, of course, a choice, > although I imagine it would be more work/require more input to do so > than to migrate a CI job. > > I use Arrow on s380x, although it's a bit of circular logic because > I'm using it to make sure nanoarrow works on big endian. > > On Thu, Apr 20, 2023 at 4:07 PM Matt Topol <zotthewiz...@gmail.com> wrote: > > > > I just wanted to add on that there was a Go on s390x job too that needs > to > > get migrated and wasn't on the list in Raul's original email. > > > > On Thu, Apr 20, 2023 at 2:42 PM Benson Muite <benson_mu...@emailplus.org > > > > wrote: > > > > > Might also consider testing farm for Centos Stream, Fedora and/or RHEL > > > builds[1][2]. > > > > > > 1) https://docs.testing-farm.io/general/0.1/test-environment.html > > > 2) > > > > > > > https://fedoramagazine.org/test-github-projects-with-github-actions-and-testing-farm/ > > > > > > On 4/20/23 19:43, Antoine Pitrou wrote: > > > > > > > > Hi Raul, > > > > > > > > I'm a bit lukewarm about this. We currently don't use Jenkins and > it's > > > > quite different from the CI services we have. Adding Jenkins jobs for > > > > s390x sounds like significant additional maintenance for a > little-used > > > > platform. Has someone been asking for this? > > > > > > > > Regards > > > > > > > > Antoine. > > > > > > > > > > > > Le 20/04/2023 à 13:00, Raúl Cumplido a écrit : > > > >> Hi, > > > >> > > > >> As discussed on this mailing list thread [1], one month and a half > ago > > > >> we migrated the ARM 64 jobs from Travis to self-hosted runners [2]. > > > >> > > > >> We are still missing to migrate the s390x jobs that we run on Travis > > > [3]. > > > >> > > > >> - name: "Java on s390x" > > > >> - name: "C++ on s390x" > > > >> - name: "Python on s390x" > > > >> > > > >> As we don't have other s390x hosts I will try and set up new Jenkins > > > >> jobs for those using the ASF provided infrastructure. > > > >> From what I can read on the ASF wiki [4] I might require some PMC > to > > > >> help me get access to Jenkins via the whimsy tool to be added to the > > > >> hudson-jobadmin group in order to have access to set up jobs on > > > >> Jenkins. > > > >> > > > >> I wanted to validate that this is ok and would like to ask if > someone > > > >> can help me with the access. > > > >> > > > >> As a reminder all Apache projects were supposed to migrate from > Travis > > > >> CI by the end of 2022 [5]. > > > >> > > > >> Thanks, > > > >> Raúl > > > >> > > > >> [1] > https://lists.apache.org/thread/mskpqwpdq65t1wpj4f5klfq9217ljodw > > > >> [2] https://github.com/apache/arrow/pull/34482 > > > >> [3] > > > >> > > > > https://github.com/apache/arrow/blob/f2cc0b41fe9fb1d8d2bdb1d2abf676278e273f55/.travis.yml > > > >> [4] https://cwiki.apache.org/confluence/display/INFRA/Jenkins > > > >> [5] https://github.com/apache/arrow/issues/20496 > > > > > > >
