Travis Ci (or any CI) + multiarch (QEMU) project + Big-endian arch enables testing on big-endian arch. As far as I know, this is the easiest way to test big-endian on the CI. ``` $ docker run --rm --privileged multiarch/qemu-user-static:register --reset $ docker run --rm -t multiarch/fedora:25-ppc64 uname -a Linux 870bdcfe1bff 4.16.15-300.fc28.x86_64 #1 SMP Tue Jun 12 00:42:35 UTC 2018 ppc64 ppc64 ppc64 GNU/Linux $ docker run --rm -t multiarch/debian-debootstrap:s390x-jessie uname -a Linux e774bfd6a08e 4.13.0-1008-gcp #11-Ubuntu SMP Thu Jan 25 11:08:44 UTC 2018 s390x GNU/Linux ``` See also my experiment for the topic: https://github.com/junaruga/ci-multi-arch-test https://github.com/junaruga/ci-multi-arch-test/blob/master/.travis.yml Maybe below mutlarch container images for Fedora and CentOS could be maintained with better way and newer version. multiarch Fedora: https://hub.docker.com/r/multiarch/fedora/tags/ multiarch CentOS: https://hub.docker.com/r/multiarch/centos/tags/ Jun On Mon, Nov 12, 2018 at 5:09 PM, Brian Stinson <brian@xxxxxxxxxxxx> wrote: > On Nov 12 13:32, Miro Hrončok wrote: >> Recently I've reported some Big Endian related test failures to an upstream >> project [0]. >> >> I was asked by an upstream project maintainer, whether I know some free >> Continuous Integration services where they can easily run their testsuite on >> Big Endian. >> >> Any tips? >> >> * Upstream uses Travis CI to test on x86_64 Linux (Ubuntu) >> * Upstream uses AppVeyor to test on Microsoft Windows >> * It's a pure Python project, noarch, but some changes need to be done when >> loading/saving binary data (LE) with NumPy on BE system. >> >> What I've considered: >> >> * COPR (but there is no big endian arch) >> * (Ab)using Koji (I guess that would be considered a bad practice?) >> * using QUEMU on Travis CI [1] >> >> Any better tips? Thanks >> >> [0] https://github.com/mikedh/trimesh/issues/249 >> [1] https://developer.ibm.com/linuxonpower/2017/07/28/travis-multi-architecture-ci-workflow/ >> >> -- >> Miro Hrončok >> -- >> Phone: +420777974800 >> IRC: mhroncok >> _______________________________________________ >> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > > This may not be helpful if you need to target S390x specifically, but we > have PPC Big-endian CentOS VMs for projects in CentOS CI: > > https://wiki.centos.org/QaWiki/CI/Multiarch > > I'm happy to chat with you and your upstream about providing some > resources here. > > -- > Brian Stinson > CentOS CI Infrastructure Team > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx -- Jun Aruga jaruga@xxxxxxxxxx IRC: jaruga, Office: TPB(Technology Park Brno) Building C 1F, Brno, Czech Republic _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
